How many endpoints does the Reddit API have?

The 59 endpoints by tier

Which endpoints most projects use

Most integrations are read-heavy, so the 31 GET endpoints at $0.002 do the bulk of the work: pulling posts and comments, resolving users, running search, and listing communities. Writes, votes, and direct messages are there when you need them, priced higher because they act on Reddit rather than just read it. See the per-call math on how much the Reddit API costs and the full tiers on the pricing page.

The read endpoints, grouped by what they return

The 31 endpoints in the read tier are where the count comes from, so it is worth seeing what they actually are. Grouped by the thing they return, they fall into five families. Unless a line says otherwise, each one is a $0.002 read.

1. Posts and listings

/api/reddit/posts lists a subreddit sorted hot, new, top, rising, controversial or best, and/api/reddit/sub/{name}/top returns top posts for a timeframe. /api/reddit/post/{id}returns one post with its comment tree, and /api/reddit/by_id/{fullnames} fetches several posts by id in one call. /api/reddit/post/{id}/visibility checks whether a post is visible outside its author's own view; it makes two upstream calls, so it is priced at $0.004, twice the read rate, rather than hiding the second call inside a single read.

2. Comments

A post's comment tree comes from /api/reddit/post/{id}/comments (with an older alias kept for existing clients) or from /api/reddit/comments when you hold a permalink instead of an id. A single comment is /api/reddit/comment/{id}, and /api/reddit/sub/{name}/comments streams the newest comments across a whole subreddit. POST /api/reddit/comments/verify takes up to 100 comment ids and reports each as live, deleted, removed or not found, billed as one read at any batch size.

3. Search

Search splits into posts, communities, comments, media and users, each its own endpoint, so a query for subreddits never returns posts you have to filter out. One search endpoint is priced above the flat rate: deep comment search at $0.02, because a single call runs a comment search and then reads the comment tree of each matching parent post, 5 by default and up to 25 with the limit parameter. At most 2 deep searches can run at once per account.

4. User profiles

/api/reddit/user/{name} returns a profile with karma, and separate endpoints return that account's comments, submitted posts and achievements. Four more listings, upvoted, saved, hidden and gilded, plus the home feed, are private to the account that owns them, so they need that account's own Reddit session rather than just your API key. They are still ordinary reads on the rate card.

5. Subreddits and communities

For a single community there are about, rules, moderators and wiki-page endpoints. For discovery there are three listings of popular, new and default subreddits, which are the usual starting point for a tool that has to suggest where a topic is discussed.

The write, vote and direct-message endpoints

The 7 endpoints in the write tier are $0.012 each: logging a Reddit account in to get a session, creating a post, posting a comment or reply (on two paths, the original and a v2), and three profile updates for the bio, the display name and the avatar or banner. Voting is its own 1 endpoint at $0.005, and the 3 endpoints for direct messages, sending one, listing threads and reading the messages inside a thread, are $0.025.

Every endpoint in this group acts as a real Reddit account, which is why it costs more than a read and why it needs the session the login endpoint returns. A tool that only reads never touches this tier, and most projects sit entirely in the read tier for their first month.

Rate limits on these endpoints

Reddit's own free Data API tier is capped at about 100 queries per minute per OAuth client and is licensed for non-commercial use, which is the limit most endpoint lists are written around. The endpoints here are not metered against that cap from your side: you send calls with one bearer key, and the connection to Reddit, including retries and proxy rotation when Reddit pushes back, runs on our side.

There is no published per-key request-per-minute ceiling on the billed endpoints. Two things still deserve a backoff in your client. A 503 means the shared upstream pool is briefly saturated. A 429 means one of three things: the same pool pushing back, a third deep comment search started while 2 are still running on your account, or Reddit throttling the account session behind an authenticated read (home feed, private listings). Every 429 carries a Retry-After header, so wait that long and retry rather than hammering it. Reddit throttling a write comes back as a 5xx error (usually a 502) instead, not a 429, with code REDDIT_RATELIMIT when you create posts too fast. And the feedback endpoint has its own limit of 10 reports per minute per key, because it files a ticket with a person behind it. The longer explanation of Reddit's limits is onReddit API rate limits.

Which endpoints an AI agent can reach over MCP

The published MCP server exposes the read endpoints as tools, so an agent in Claude, Cursor or another MCP client can search, read posts and comments, and look up users and subreddits without HTTP code. It also exposes the free monitor and feedback tools. The write, vote and DM endpoints are not on the MCP tool surface; they stay REST calls your own code makes, so a model choosing tools cannot post or vote by itself. Setup is on theReddit MCP server page.

Batch comment verification: 100 ids in one read

One read endpoint does the work of a hundred. The batch verify endpoint takes up to 100 comment ids in a single POST and tells you, for each one, whether it is live, deleted, removed or not found. It is a POST only because a hundred ids do not fit in a query string; it bills at the read rate, $0.002, whatever the batch size.

That matters for anyone who has to prove comments are still up: a community team checking that its replies survived moderation, a researcher cleaning a dataset of removed content, or a tool reporting on placements. Checking 10,000 comments one at a time would be 10,000 reads; batched, it is 100 reads, or $0.20. Endpoint counts treat this as one endpoint among 59, which is exactly why a count on its own says little about what an API can do cheaply.

Fan-out pricing: deep search and visibility checks

Two reads are priced above the flat rate, and both for the same reason: one call to us turns into more than one call to Reddit. Deep comment search, at $0.02, runs a comment search and then reads the comment tree of each matching parent post, 5 by default and up to 25 with the limit parameter, so you get the matching comments with the conversation around them in one response. Because each one holds several upstream sessions, at most 2 can run at once per account; a third waits briefly and then gets a 429 that is not billed. The post visibility check, at $0.004, makes exactly two upstream calls: it reads the post by id to learn who wrote it, then reads one page of that author's submitted posts to see whether the post still appears where other people would find it.

The rule behind both prices is that a call costs what it does upstream. A check that needs two Reddit requests is priced at two reads rather than hidden inside one, and a search that fans out into as many as 25 tree reads is priced to match. When you estimate a bill, count these two endpoints separately; everything else in the read tier is the flat $0.002.

One bearer key across every tier

All 59 endpoints sit behind the same credential: one API key sent as a bearer token. There is no separate scope to request for writes, no second product to enable for direct messages, and no different key for the free account and feedback calls. What changes between tiers is the price per call and, for writes, votes and DMs, the Reddit account session the login endpoint returns, because those calls act as a real account. Reads need nothing beyond the key, so a project can start on the read tier and add a write later without re-provisioning anything.

The 15 endpoints you are never billed per call for

15 endpoints of the 59 endpoints cost nothing per request, and they are three different things rather than one free tier.

2 endpoints are account reads. /account/me and /account/payments return your own key status and billing history, and they are free on every plan so that checking what you have spent never becomes part of what you spend. Poll them as often as a dashboard needs.

3 endpoints are feedback. POST /feedback takes a bug, idea or missing-capability report and GET /feedback/{id} reads whether the team triaged, shipped or declined it. They exist for AI agents: the official MCP server drafts a report the moment a tool fails or a capability is missing and sends it only after you review the draft, so telling us what broke never costs a credit.

The other 10 endpoints are the monitoring surface: creating and updating keyword monitors, listing them, checking their health, reading deliveries, and managing webhooks. Those are billed by plan rather than per call, so a monitor that fires a thousand times does not bill a thousand times. Free per call is not the same as free, and this is the tier where that distinction matters.

How to check the number yourself

Endpoint counts are the easiest number in developer marketing to inflate, so here is where ours comes from. The 59 endpoints is the number of paths in the OpenAPI document we publish at docs.redditapis.com/openapi.json. Fetch it and count the operations, one per HTTP method on each entry under paths, and you should get the same figure as the table above. Count the path keys alone and you get one fewer, because the feedback path carries both a POST that sends a report and a GET that lists them. The health probe is deliberately excluded, because a status check is not something you build against.

The tier counts add up to the total on purpose: 31 endpoints reads, 7 endpoints writes, 3 endpoints direct-message endpoints, 1 endpoint vote endpoint, and 15 endpoints unbilled. If a breakdown does not sum to the headline, one of the two numbers is decoration.

Frequently asked