Veezee

Tweet lookup API 4 credits

Fetch a single tweet by id or URL: the text, full engagement metrics (views, likes, retweets, quotes, replies, bookmarks), language, and the quoted tweet inline when there is one. The id is the digits after /status/ in any tweet URL.

It costs 4 credits. The typical use is verification: confirm a tweet exists and check its engagement before citing it, or follow a quote chain hop by hop.

Try it now#

No account, no card: mint a free key in one call, then call the endpoint.

Terminal
curl -s -X POST https://api.veezee.io/v1/keys/mint
Request
curl "https://api.veezee.io/v1/x/tweet?tweet_id=2054497961162478079" \
  -H "Authorization: Bearer $VEEZEE_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"

Over MCP#

Point an MCP client at https://mcp.veezee.io/x (streamable-http; https://mcp.veezee.io/all serves every platform over one connection) and call x_get_tweet:

tools/call
{
  "method": "tools/call",
  "params": {
    "name": "x_get_tweet",
    "arguments": {
      "tweet_id": "2054497961162478079"
    }
  }
}

Parameters#

ParamRequiredTypeDescription
tweet_idyesstringNumeric tweet id, e.g. '2054497961162478079', or a full tweet URL.
freshnessnostringrecent (default) serves cached data from the last few hours when available; realtime forces a live fetch for +2 credits (refunded if we fall back to cached data). Trial keys are cached-only and reject realtime with TRIAL_CAP_EXCEEDED; paying upgrades this same key to unlock it.
max_creditsnointegerSpend ceiling for this one call. The call is rejected (nothing charged) if its quote exceeds this. Only the quote is ever reserved, never this ceiling.

Returns a x_tweet envelope. Full field list: /docs/fields#x_tweet.

Pricing#

x_get_tweet costs 4 credits base per call (surcharges for optional sections, cursor pages, and batches are in the full reference). Every key starts with a free budget of 200 credits per IP per day, no account, no card; past that, credits are $2.00 per 1,000 with no subscription required.

FAQ#

Does it return the replies underneath?

No: one tweet per call. Search the conversation with x_search or read the author's timeline.

Can I pass a full URL?

Yes, tweet URLs are accepted; the URL resolver handles messier forms offline.

Batch lookups?

One tweet per call; loop client-side.

Read next#