X Search API for posts
Search X posts over HTTP and receive the account handle alongside each result, without an X developer account or a per-tier post cap.
Endpoint
Results arrive in the same JSON shape as every other engine, so existing parsing continues to work.
The title reads like OpenAI (@OpenAI).
The link points at the post on x.com.
The snippet is the text of the post itself.
Useful for
Announcements / Sentiment / Monitoring
Where announcements land first
Set `search_service` to `x` and the results come from X posts. The endpoint, the authentication, and the response shape are the same as every other engine, and no X developer account is involved.
Handle in the title
The `title` field carries the display name and the `@handle`, so the account is parseable without a second call.
Post text as the snippet
The `snippet` field is the post itself rather than a description of it, which is usually the whole answer for a short announcement.
No developer account or post cap
Requests are billed against Search1API credits rather than an X API tier, so there is no monthly post allowance to plan around.
Standard Search parameters
`max_results` up to 50, plus `include_sites`, `exclude_sites`, and `time_range`.
What is an X search API?
An X search API is an HTTP interface that returns posts from X as structured results. X operates its own API with paid access tiers and monthly post caps, which makes exploratory and low-volume use awkward to budget for. Search1API exposes X as one of the search services on its Search endpoint, returning the display name and handle in the title, the post link, and the post text as the snippet, in the same JSON shape it returns for its other engines. For agents, X matters because product announcements, incident notices, and pricing changes frequently appear there before they reach a company blog or the open web.
Typical workflow
Search X posts over HTTP and receive the account handle alongside each result, without an X developer account or a per-tier post cap.
Send a query with `search_service` set to `x`.
Read the account from `title` and treat `snippet` as the post text.
Use `time_range` to restrict results to recent posts when recency is the point.
One request, posts with their account
A single call searches X posts and returns the account handle with each result, so an answer can attribute a claim to the account that made it.
bash
Best for
AI assistants that need announcements before they reach a blog post.
Brand and competitor monitoring across accounts.
Incident tracking where the first signal is a post rather than a status page.
Sentiment analysis around a launch or a pricing change.
FAQ
Do I need an X developer account?
No. Authentication is your Search1API key. The request is a POST to https://api.search1api.com/search with `search_service` set to `x`.
How is this different from the X API?
X sells access in tiers with monthly post caps. Search1API bills per request against its own credits, so low-volume and exploratory use costs what it costs rather than requiring a tier commitment. The trade-off is that this returns search results rather than the full X API surface, so it does not cover posting, streaming, or account management.
Can I get the full post or thread?
The snippet is the post text, which is the whole post for most results. Set `crawl_results` when the workflow needs the rendered page, and each page retrieved successfully includes a `content` field with the text as markdown.
What does an X search cost?
One credit per search, and one additional credit for each page retrieved successfully through `crawl_results`. At the base top-up rate of $1 for 1,000 credits, that is $1 per 1,000 searches. Signup includes 100 free credits with no credit card.
Can I search posts from a specific account?
Put the handle in the query itself. The account is also returned in the title, so results can be filtered after the fact.
Which other community sources are supported?
The same Search endpoint accepts `reddit` for discussion, `github` for repositories, and `youtube` for video, alongside general web engines and the Chinese-language engines, for 17 engines in total on one contract.