Building on the free tier without hitting a wall

By Devran Koç Published September 20, 2026 Updated October 19, 2026 2 min read

Short answer

The free X API tier is built for a single-user tool, not a public service. It gives you posting tied to your own account with tight read caps, so design for it by caching every response, polling on a timer instead of a loop, and reading the rate-limit headers to back off before a 429. For posting, X documents a limit of 200 requests per 15 minutes and 300 per 3 hours.

Key takeaways

  • The free tier suits a personal, single-account tool, not a multi-user service.
  • X documents a posting limit of 200 requests per 15 minutes and 300 per 3 hours.
  • Cache aggressively; most rate-limit problems are really duplicate-request problems.
  • Read x-rate-limit-remaining and back off before you hit zero.

You can learn the API and run a small tool without paying, as long as you design around the caps from the start rather than discovering them in production. Here is what to plan for.

What does the free tier actually allow?

The free tier is scoped to your own account, with posting and a small read allowance. It is meant for a single-user tool or for learning, not for a service that reads thousands of timelines. Access tiers and their exact caps change over time, so confirm the current numbers on X’s developer portal before you commit to a design.

What are the posting rate limits?

X documents a user-level posting limit of 200 requests per 15 minutes, plus 300 per 3 hours across posts and retweets. Deletes have their own limit of 50 per 15 minutes. These are the numbers to design against: a tool that posts in a burst will hit the 15-minute cap long before the 3-hour one.

How do you design around the caps?

Cache anything you read more than once, poll on a timer rather than in a loop, and watch the rate-limit headers. Every response carries x-rate-limit-remaining and x-rate-limit-reset; back off when remaining gets low instead of waiting for a 429. The rate-limits chapter has the exponential-backoff code.

Do not put a Bearer token in client-side code to avoid running a backend. A tiny token proxy is far cheaper than a leaked key.

Sources

  1. Manage Posts: rate limits, X Developer Platform documentation.

Frequently asked questions

Can I run a public bot on the free tier?

Not comfortably. The free tier is scoped to your own account with tight read caps. A public, multi-user service needs a paid tier.

What happens when I hit a rate limit?

The API returns HTTP 429. Read x-rate-limit-reset for when your budget refills, and retry after that with backoff.

How many posts can I make per 15 minutes?

X documents 200 POST requests per 15 minutes at the user level, and 300 per 3 hours across posts and retweets.

Does caching really matter that much?

Yes. Most rate-limit problems are duplicate-request problems. Caching a response you would otherwise fetch again is the single biggest saving.

Where do I check current tier limits?

On X's developer portal. Tiers and caps change, so treat any number you read in a blog post, including this one, as a starting point to verify.