Use case, X (Twitter) search

X (Twitter) search API for your agent. One call per search.

Send a search query with optional operators. Read post text and author back. Your agent picks the provider, and you pay per call.

Give this to your agent
set up looot for X (Twitter) search API - https://looot.ai/use-cases/twitter-search-api/skill.md

The short answer

The short answer

X (Twitter) search API for an agent: it sends a search query with optional operators to a catalog endpoint and reads post text, author and likes back. Several providers sell the call, so the agent tries the cheapest first. You pay per call, and a failed call costs nothing.

Updated

  • Post text
  • Author
  • Likes, replies and reposts
  • Post date
  • Post link

The job

What the X (Twitter) search API gives your agent

X search finds what people are saying, with the operators power users know: from:, since:, until: and a minimum like count. Your agent sends the query and reads back the posts with their text, author and engagement. It is the base for brand monitoring, customer research and finding the posts worth replying to.

Three providers answer. One accepts the full advanced-search syntax inline and returns about 20 posts per page. One takes the filters as separate fields: exact phrase, any of these words, from these accounts, language, media type and a minimum of likes or replies. One takes a keyword and a search type.

You give

a search query with optional operators

claude code min_faves:50

You get

  • Post text
  • Author
  • Likes, replies and reposts
  • Post date
  • Post link

Providers, cheapest first

What actually differs between providers

Today the price runs from $0.00075 to $0.0010 across 2 endpoints. The dearest costs about 1.3 times the cheapest. Price is only one difference. Each entry below says what that endpoint takes or returns that the others do not.

  1. AnyAPI logoAnyAPI

    Accepts the full X advanced-search syntax in the query, returns posts with text, author and engagement, and pages with a cursor.

    anyapi-run-twitter-search
    $0.00075 / call
  2. TikHub logoTikHub

    Takes a keyword and a search type and pages with a cursor.

    tikhub-api-twitter-web-fetch-search-timeline
    $0.0010 / call
  3. Any Site API

    Takes separate filters for exact phrase, any of these words, accounts, language, media type and minimum likes or replies, and bills per result.

    anysite-api-twitter-search-posts
    price on request

Cost

What 100 X (Twitter) search runs cost

$0.0750

100 searches cost about $0.0750 through the cheapest endpoint, at AnyAPI, and about $0.1000 through the dearest. Each run is one call.

Sample calls

The request and what comes back

Each run is one POST to /v1/runs with an endpoint id and an input. These are illustrative calls with generic values. The run's result holds the provider's own fields.

Request
{"endpointId":"anyapi-run-twitter-search","input":{"query":"claude code min_faves:50","limit":20},"wait":30}
ResponseSample output
// POST /v1/runs, then read run.status and run.result
// result: accepts the full X advanced-search syntax in the query, returns posts with text, author and engagement, and pages with a cursor

The prompt

Copy one prompt, give it to your agent.

Edit the names and numbers, paste it, and the agent runs the job and shows the cost.

  • One run is one search.
  • 1 step across 3 providers.
  • Runs on demand, whenever you ask.
Prompt: X (Twitter) search API
Use looot to search X for claude code min_faves:50 over the last month, and return the text, author, likes and link of each post. 1. Set up https://looot.ai/skill.md. 2. Search the catalog for each step and check its price before you call. 3. Run the cheapest endpoint that fits. 4. Show the results as a table and the total cost.

Give this to your agent
Setup command
set up looot for X (Twitter) search API - https://looot.ai/use-cases/twitter-search-api/skill.md

Before you start

Settle these before the first run

  • Write the query with operators. Bare terms match broadly, and from:, min_faves: and a date window cut a search to the posts that matter.
  • Page with a cursor. A page holds about 20 posts on one provider, and a longer pull means several calls.
  • Be careful with replies. A search that mixes posts and replies is noisy, so use the media and engagement filters.

FAQ

Questions people ask

Find the posts worth a reply, follow mentions of a brand and collect the questions people ask. Your agent keeps the post link as the source.

Send a query to an X search endpoint. Your agent reads the posts as JSON with the text, the author and the engagement, and pages with a cursor.

Yes, on one provider that accepts the full syntax inline, including from:, since:, until: and min_faves:. The others take the same filters as separate fields.

Yes. Use the from: operator, or the from-these-accounts filter on the provider that has one. The catalog also has user-timeline endpoints for the full feed of an account.

About 20 per page on one provider. Your agent follows the cursor to fetch more, and each page is billed as a call.

You pay per call, and the price depends on the provider your agent picks. This page reads the cheapest live price from the catalog and shows no number when the catalog is unreachable.

No. A call that fails at the provider costs nothing, and your agent can retry it or send it to another provider.

No. One looot key reaches every provider in the catalog. You top up once, and each call is billed at the price shown before it runs.

Send a POST to /v1/runs with the endpoint id, the input and a new idempotency key, and your looot token in the Authorization header. With wait set to 30, the answer comes back in the response when the run ends within 30 seconds. Otherwise poll GET /v1/runs/<runId>.

That needs scheduled runs, not available yet. Run it by hand whenever you want fresh results.

No. looot bills per call, and nothing runs while your agent is idle.

More ways to run this job

For agents
use case
X (Twitter) search API
run
search
schedule
on demand
step
Search posts on X: anyapi anysite tikhub
setup
https://looot.ai/use-cases/twitter-search-api/skill.md
llms.txt
https://looot.ai/llms.txt
updated
2026-10-04

Try X (Twitter) search with your own agent.

Start your workspace, top up, and paste the prompt into the agent you already use.