These Terms of Service (“Terms”) govern access to the threadapi websites, dashboard, documentation, and API at threadapi.dev, api.threadapi.dev, and docs.threadapi.dev (together, the “Service”).
The Service is operated by the person or company that runs those hostnames and charges you through the Stripe account named on your threadapi receipt (“threadapi”, “we”). Notices under these Terms go to hello@threadapi.dev. The registered legal name and postal address of that operator, once published, will be added to this page and will identify the contracting party. Until then, the contracting party is the operator of those hostnames.
1. Acceptance
Creating an account, generating an API key, buying credits, or sending a request to the API is acceptance of these Terms. You confirm that you are legally able to enter this agreement and, if you use the Service for an organization, that you can bind that organization. The organization and the person who accepts are both responsible for use of the Service under that account.
2. The Service
threadapi is a developer API, with an MCP server, for public Reddit content: posts and their comments, subreddit listings, and search results. It is an independent service. It is not Reddit and is not endorsed by Reddit, Inc.
Responses are produced from Reddit pages that are publicly available to logged-out visitors, fetched through our own infrastructure. We do not use any Reddit user’s account, we cannot fetch private, quarantined, or age-gated content, and we do not provide a general-purpose proxy: a customer API key cannot be used to reach arbitrary URLs.
We may change, suspend, or withdraw an endpoint, a response field, or the Service. When a change breaks a documented request, we will describe it in the documentation or the changelog. There is no uptime commitment unless we have signed a separate written reservation with you.
The public demo on the marketing site is rate-limited and is not the paid API.
3. Accounts and credentials
You need an account to create API keys and to use the dashboard playground. Signup is by a one-time code sent to your email, or by Google or GitHub. An AI agent you use can also start a signup for you; the account and its key are created only after the code we email you is entered. You are responsible for the keys issued on your account. A key is shown in full once. Store it as a secret. Requests made with your key, including requests made by a person you shared it with, are yours.
You may revoke a key in the dashboard. Revocation takes effect as soon as the API observes it, which can take up to a minute.
We may refuse, suspend, or close an account or key that breaks these Terms, that we reasonably believe is fraudulent, or that puts the Service, Reddit, or our hosting providers at risk.
4. Credits
Credits are a digital balance used to pay for successful billed API responses. New credits are added only as the packs listed on the pricing page. We do not sell custom amounts, and there are no subscriptions.
Signup includes 100 credits, once per email address. An address that already received them, including through a deleted account or another spelling of the same mailbox (such as a +tag), does not receive them again, and we may limit how many new accounts on one email domain receive them each day, or pause signup credits for a day when signups look automated. You do not add a card to receive them. Purchased credits and unused signup credits do not expire. They are a balance we still owe you if the Service stops, not a promise that a particular post or subreddit will remain available.
A successful response on a billed endpoint costs the number of credits stated on the credits page in the documentation at the time of the call. Today, that schedule is:
- one credit for a successful post response with up to 500 comments, and one more credit for each further 100 comments, or part of 100, that the response returns;
- one credit for a successful subreddit listing or search response;
- ten credits per day for a running keyword monitor (up to 20 keywords);
- the same for a call through the MCP server as for the route it calls;
- the same for a response served from cache as for one fetched from Reddit.
You are billed for what a response returns, not for the requests we make to produce it. If your balance covers fewer comments than you asked for, the response returns what the balance covers. Failed responses, including client errors, removed or private content, rate limits, and upstream errors, cost zero credits. A request you retry after a success is a new request and is billed again if it succeeds.
Customer Cache-Control: no-cache and no-store headers do not bypass the cache. Cache policy is ours.
The dashboard playground and test deliveries you trigger are billed from your balance like API calls.
5. Refunds
If you are a consumer in the European Economic Area or the United Kingdom, you have a statutory right to withdraw from a purchase within 14 days without giving a reason. By buying credits and asking for them to be added to your balance immediately, you agree that we supply the digital content straight away. You keep the right to withdraw within 14 days, and we will refund any credits of that purchase that you have not used.
Outside those statutory rights, we will refund a purchased credit pack within 14 days of purchase if none of its credits have been spent. After credits from a pack have been spent, or after 14 days, purchases are non-refundable.
To ask for a refund, email hello@threadapi.dev from the account address, with the Stripe receipt number. We refund to the payment method used.
6. Rate limits and capacity
Requests are rate-limited to protect the Service and other customers. Limits depend on the largest pack you have bought and are described on the pricing page. A free key is also subject to a daily request cap. We may apply temporary lower limits during high-load periods or incidents.
A request rejected for rate limiting (HTTP 429) costs zero credits. You will not attempt to bypass rate limits by creating multiple accounts or rotating IP addresses.
7. Reddit content and intellectual property
We do not own Reddit content. Posts, comments, user names, subreddit titles, and media linked from responses are the property of Reddit, Inc. or the Reddit users who posted them.
You are responsible for what you do with the data you retrieve. You will comply with all laws that apply to your storage, processing, and republication of that content, including personal data in public posts and comments, and for honouring deletions where the law requires it.
Do not present the Service, or data from it, as an official Reddit product.
8. Acceptable use
You will not:
- break the law, or help someone else break it;
- use the Service to harass, dox, or harm a person;
- send card-testing, credential-stuffing, or other attack traffic;
- bypass a security control, probe the Service as an open proxy, or overload it in a way that is not a good-faith measurement with your own key and credits;
- resell or white-label the Service without our written permission;
- share an API key publicly.
We may suspend access while we investigate a breach of this section.
9. Availability and third parties
The Service depends on Reddit and on Cloudflare, and on the network between them and us. Those parties can change their systems, block traffic, or remove content. We will use reasonable efforts to keep the API working. We are not liable for a failure or a change caused by Reddit, Cloudflare, Stripe, a network provider, a denial of service, a legal order, or any other cause we do not control.
Cached copies of fetched threads are stored for at most seven days, and for minutes when a thread is new, so a later request can be answered quickly.
10. Intellectual property
The API, dashboard, documentation, and the software that runs them are ours or our licensors’. These Terms give you a limited, non-exclusive, non-transferable, revocable right to call the API and to use the dashboard for your own applications. They do not give you ownership of the Service.
11. Disclaimer
The Service and the data it returns are provided “as is” and “as available”. We do not warrant that a thread or its comments are complete, that content will remain available, that analysis such as the discussion digest is accurate, that a response is fit for a particular purpose, or that the Service will be uninterrupted or error-free. Mandatory rights you have as a consumer are not affected.
12. Liability
Nothing in these Terms limits liability that the law does not allow us to limit, including liability for fraud, or for death or personal injury caused by negligence.
Where a cap is allowed, our total liability arising out of the Service in any 12-month period is limited to the amount you paid us for the Service in that period. If you have only used free credits, that cap is zero to the extent a zero cap is enforceable, and otherwise it is the minimum the law requires.
We are not liable for lost profits, lost goodwill, lost data, or indirect or consequential loss, or for the cost of a substitute service, whether we knew the loss was possible.
13. Indemnity
If you use the Service for a business, you will indemnify us and our contractors against claims, damages, and reasonable legal costs arising from your use of the data, your breach of these Terms, or your violation of someone else’s rights. We will tell you about the claim and let you control the defense, provided the settlement does not admit fault on our behalf without your agreement and ours.
14. Privacy
We process account, billing, and API data as described in the Privacy Policy. If you use the API to obtain content that includes personal data, you are responsible for your own legal basis. Business customers who need a data processing agreement can request one at hello@threadapi.dev.
15. Changes to these Terms
We may update these Terms by posting a new version on this page with a new date. If a change materially reduces your rights, we will also send a notice to the email on the account or post it in the dashboard before it applies. Continuing to use the Service after the effective date is acceptance of the new Terms. If you do not agree, stop using the Service and write to us about any unused credits.
16. Governing law
If you are a consumer in the EEA or the United Kingdom, you keep the mandatory rights of your country of residence, including any cooling-off rule that still applies after you agree to immediate supply of digital credits.
For every other dispute, the law of the country where the operator has its registered seat or habitual residence applies, without conflict-of-law rules that would select another country’s law. The courts of that place are the venue, except where a consumer statute lets you sue where you live.
17. General
These Terms are the whole agreement about the Service, except for a written capacity reservation or a data processing agreement we sign with you. If a court holds one provision unenforceable, the rest stays in force. Waiting to enforce a provision is not a waiver. You may not assign these Terms without our consent. We may assign them to a successor of the Service.
Version 1.0, 10 October 2026