Veezee

X URL resolver 2 credits

Classify any x.com or twitter.com URL, mobile links, query params, /i/web/status forms, as a profile or a tweet, and get the handle or numeric id the other X endpoints need. It parses offline without fetching the page.

It costs 2 credits. Skip it when you already hold a handle or tweet id: the fetch tools accept those directly.

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/resolve-url?url=https%3A%2F%2Fx.com%2Fnasa%2Fstatus%2F2054497961162478079" \
  -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_resolve_url:

tools/call
{
  "method": "tools/call",
  "params": {
    "name": "x_resolve_url",
    "arguments": {
      "url": "https://x.com/nasa/status/2054497961162478079"
    }
  }
}

Parameters#

ParamRequiredTypeDescription
urlyesstringAn X URL, e.g. https://x.com/nasa/status/2054497961162478079 or https://twitter.com/nasa.

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

Pricing#

x_resolve_url costs 2 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#

Can it expand t.co short links?

No: t.co can't be expanded offline, and the call returns INVALID_INPUT saying so. Expand the link in your own fetch step first.

Do old twitter.com URLs work?

Yes, both domains and their mobile forms.

What next per result type?

tweet goes to the tweet lookup API; profile to the profile API or timeline.

Read next#