Skip to main content
AI agents and scripts can call our read-only endpoints without signing up. Each request is paid on its own, in USDC, using the open x402 standard (HTTP 402 Payment Required).
For regular or high-volume use, an API key is cheaper per request. x402 is for no-signup, pay-as-you-go access.

Endpoints and prices

The response body is the same as the regular endpoint in the last column, and only the parameters listed above are used. Payment networks: Base USDC and Solana USDC.

How it works

  1. Send the request with no payment. You get HTTP 402 with a PAYMENT-REQUIRED header (base64 JSON) that lists the price, the accepted networks and the address to pay.
  2. Your x402 client signs a payment for that exact amount and sends the same request again with the payment in the PAYMENT-SIGNATURE header.
  3. The payment is verified, the data is fetched, and you get HTTP 200 with the data.
In practice, use any x402 v2 client library. It handles steps 1 and 2 for you.

When you are not charged

The payment is only completed after the data request succeeds. You are not charged when the request returns an error, including:
  • HTTP 400 for a missing or invalid parameter, including more than 20 tweet_ids or userIds, or a count above 50;
  • HTTP 4xx or HTTP 502 when the data request fails.
A successful request is charged even if it returns no results. Tweet IDs that are deleted or not found are left out of the result, and the request is still charged. Every paginated endpoint returns one page per request; use cursor from the response to get the next page, and each page is a new paid request. Each payment authorization can be used once. Sending the same payment again returns HTTP 402 (Payment already used).