Terms of use for the API

1. This agreement

These terms cover the Everything Blog API (the "API") served at api.everythingblog.in and the developer dashboard at everythingblog.in/developers. Using an API key means accepting them: creating a key is the signature, and the account holder is responsible for everything done with every key on the account, including keys issued to employees, contractors and customers.

Paid plans are sold and invoiced by Dodo Payments as merchant of record. Its terms and refund policy apply to the payment relationship; these terms apply to the API itself.

2. What you may do

Build products on the API: read the feed, search, cluster related coverage and use the AI analysis to explain stories to your own users — commercially, on as many of your own products as you like.

• Display headlines, TL;DRs, key points, sentiment and metadata from the API.
• Store and cache responses, including duplicating the story data in your own database.
• Charge your own users for your product, and put advertising in it.
• Send end users to the original publisher using the source URL returned with every item.

3. What you may not do

The API aggregates third-party journalism. Our right to distribute the analysis is not the same as a right to republish other publishers' work in full, so:

• Do not republish full article text, in any form, unless we have signed a written agreement with you for it. Full text is not sold on the standard plans for exactly this reason.
• Do not present AI-generated summaries as the publisher's own words, and do not remove or hide the source attribution that the data makes possible.
• Do not build a substitute for the publishers' own sites: no mirroring their full text, no reproducing their pages, no scraping their sites through us.
• Do not bypass limits: no multiple accounts or keys to evade a rate limit or quota, no automated key rotation against the same budget, no proxying the API to third parties under a quota bought for your own product.
• Do not use the API for unlawful content, harassment, targeted disinformation, or to build profiles of individuals. Analytics payloads you send us must not contain personal data you have no basis to collect.
• Do not attempt to obtain keys or data belonging to another account, probe the API for vulnerabilities without our written permission, or use the API in a way that degrades it for others.

4. Attribution and AI disclaimer

Attribution is a condition of use: show the publisher name and link the story to its source URL (every feed item includes one), and credit Everything Blog where it is reasonable to do so, for example a "Powered by Everything Blog" link on a page that displays our data.

Summaries, key points, sentiment scores and categories are machine-generated reading aids. They can be wrong. You must not present them as verified facts, and where your users could act on a claim that matters, link them to the source so they can check it.

5. Limits, quotas and fair use

Your plan's rate limit and monthly allowance are enforced server-side and documented in the API reference. Requests beyond the allowance are refused, not billed; overage happens only after you set a spend cap, and never beyond it.

If you need more than your plan allows, upgrade or write to us. Sustained attempts to obtain more usage than a plan provides — including distributing a single key across unrelated parties — may result in rate limits being tightened or the account being suspended, with notice when circumstances allow.

6. Data retention and privacy

What we store: your account (a username, an optional email address, a hashed password and hashed API keys), your subscription state, and your usage counts. We never store card data — the payment provider does.

Usage and invoice-related records are kept for as long as your account exists. They are the basis of your invoices and of any billing dispute, so we cannot delete them on request while an invoice could be challenged; when you close your account we delete the account and its keys, and keep only what tax and accounting rules require us to keep.

Request logs (the API's audit log: key creation, rotation, revocation, plan changes, checkout starts) are kept for as long as the account exists, so you can always reconstruct what happened to your own account. We do not sell or share this data, and we do not use your usage data to build a profile of your end users.

Data you send in event payloads is stored with your events. You control what you send, and you must have a lawful basis for anything personal you include.

To ask what we hold about you, or to have your account deleted, write to hello@everythingblog.in.

7. Availability, changes and suspension

Self-serve plans are provided as-is and do not carry a service level agreement. We work to keep the API up and publish what is currently working on the status page, but the free and standard plans come with no uptime commitment and no credit for downtime. Enterprise agreements can include an SLA — ask.

We may change these terms. Material changes affecting how you may use the API are announced at least 30 days in advance by email to the account's address and in the changelog; continuing to use the API after that date means accepting the new terms.

Prices change with 30 days' notice for the next period; a subscription runs at the price it was bought at until it is renewed or changed. Annual subscriptions keep their price until the year ends.

We may suspend or end access for a breach of these terms, for non-payment, or where the law requires it. Where the problem can reasonably be fixed, we will tell you what it is and give you time to fix it.

8. Liability

The API is provided without warranties about the accuracy of third-party content or of machine-generated analysis. To the extent the law allows, our total liability is limited to the fees you paid us in the twelve months before the claim, and we are not liable for indirect or consequential loss, including lost profits or lost data.

Nothing here excludes liability that cannot be excluded by law.

9. Governing law

These terms are governed by the laws of India. Enterprise agreements name a specific forum; for everything else, disputes are subject to the jurisdiction of the Indian courts that would hear them under ordinary rules.

Questions about any of this — including a full-text licensing agreement — are welcome at hello@everythingblog.in. This page is a plain-language statement of the actual policy, not legal advice.