WEIR

Free tool

X advanced search builder

Fill in the fields once and copy the search for x.com, the official X API v2, or Weir's API. It runs in your browser, with no account.

Words
Accounts
Filters
Dates (UTC)

x.com search box

from:XDevelopers min_faves:20 -filter:replies

X API v2 query

from:XDevelopers min_likes:20 -is:reply

Weir API request

curl https://api.weirapp.io/v1/x/search \
  -H "Authorization: Bearer $WEIR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"fromUsers":["XDevelopers"],"minLikes":20,"onlyOriginal":true,"sort":"latest","limit":20}'

One search, three dialects

X’s search box, the X API v2 and Weir each read X’s search operators a little differently. The builder writes each version from the same fields.

Every operator is explained, with tested examples, in our guide to Twitter advanced search operators. To price a search before you run it, use the X API cost calculator.

Questions

Why does the X API need a different query?

X's API uses its own operator names. Its operator docs say min_faves: and min_retweets: are rejected with a 400 error, so the builder writes min_likes: and min_reposts: instead. Dates become the start_time and end_time parameters rather than since: and until:.

Why does my search return nothing on x.com?

Try one operator at a time, because X changes search without notice. Use underscores, not hyphens, inside url: values, and keep to about 22 operators in one query.

Is what I type sent anywhere?

No. The queries are built in your browser. Nothing leaves the page until you open the x.com link or run a request yourself.

Can I run the search from code?

Yes. The X API query works with X's search endpoints, which charge $0.005 per post read as of October 2026. The Weir request runs on a free key with 5,000 credits a month, at 1 credit per post plus 1 per call.