How this site works

PrimaryAPI publishes xapipricing.com, and the site’s pick is PrimaryAPI, the product we make. That makes this a company’s own reference page, not an independent review, and every page says so. Weigh the recommendation accordingly, and use the checklist below to compare any option on its merits.

These are the questions we think matter for X API pricing, whichever option you choose:

• Know the billing unit. Find out whether you pay per request, per call or per item returned. On a per-item rate card, a search that fills a page is charged once for every post on it.
• Count what each job returns. Estimate a month from the items each job brings back (posts, users, followers), not from the number of requests you send.
• Check the monthly ceiling. Ask what the monthly limit is and what happens when you reach it: blocked requests, an upgrade or a new contract.
• Ask how repeats and misses are billed. Check whether reading the same item twice is charged twice, and whether an empty or failed response costs anything.
• Cap spend before you scale. A prepaid balance, a spending limit per cycle or a credit limit per key keeps one runaway script from draining the budget.

API names, the fields they return and their prices come from the PrimaryAPI catalog, the same data that powers primaryapi.com/apis. They come straight from the catalog when the site is published, never typed in by hand, and an API that cannot be called right now drops off the lists within minutes.

Facts about the official X API were read from X’s published pages on November 14, 2026. Each one links to the page it came from, and any fact from a secondary source says so.

Reliability figures for every PrimaryAPI API, measured from real calls, are public on primaryapi.com/network.

This site’s copy was last reviewed on November 14, 2026. We update it when the facts change. If something here is out of date or wrong, email [email protected] and we will correct it.