Key takeaways
- Inoreader API access needs the Pro plan, $7.50 a month billed annually or $9.99 monthly, unless you build a public app.
- Default Pro limits are 100 requests per day in each of two zones; higher limits need a custom plan.
- AyeWatch paid plans, from $9 a month, include a REST API, HMAC-signed webhooks and an MCP server, so code is notified instead of polling.
Inoreader API pricing is not on a separate price list. Access comes with the Pro plan, which costs $7.50 a month billed annually or $9.99 billed monthly, and the default limits are small: 100 requests a day in each of the two API zones. Anything more needs a custom plan quoted by sales. If what you actually want from the API is "notify my code when something relevant is published," a push-based service such as AyeWatch, with webhooks on paid plans from $9 a month, is often a better fit. Here is the detail, checked on both vendors' pages in October 2026.
What Inoreader's API includes
Inoreader's developer portal says API access is granted to developers building publicly available apps on platforms Inoreader does not cover. For everyone else, "an Inoreader Pro plan is required." The API is a reader API. Its methods let you:
- read user info, unread counts, the feed list and the folder and tag list
- add and edit feeds
- read stream contents and item IDs
- set stream preferences, rename, edit and delete tags
- mark all items as read
Authentication uses OAuth 2.0 for users plus an application registration.
Rate limits on Pro
| Zone | Default Pro limit |
|---|---|
| Zone 1 | 100 requests per day |
| Zone 2 | 100 requests per day |
Limits are counted daily, and every response carries headers with your limit and current usage. Higher limits are only available for public apps or by buying a custom Inoreader plan. Team plans include one shared developer application at default limits, with more as add-ons.
At 100 calls a day, a script that polls one stream every 15 minutes uses 96 of them. Two streams and you are over.
The polling problem
The bigger cost is architectural. A reader API makes you poll: ask for new items, filter them yourself, decide what matters, repeat. You end up writing the relevance logic that the reader's rules were supposed to handle, inside a daily request budget.
The webhook-first option: AyeWatch
AyeWatch is an AI monitor that pushes instead of waiting to be polled. You define topics in plain English, for example "a breaking change or deprecation in the Stripe API," and AyeWatch checks news sites, forums, blogs, social platforms and specific URLs. AI judges each new item by meaning and, when it matches, creates a short summary with sources.
On every paid plan you get:
- A REST API to create, list, update and delete topics, so monitors live in your repo or deploy scripts.
- Webhooks.
topic.updateevents carry the AI summary and are HMAC-signed for verification. - An MCP server at
https://ayewatch.ai/api/mcp, used with an AyeWatch API key, so an AI agent can set up or read monitors. - Slack, Discord and email as other channels, set per topic.
Your code receives a signed POST when something relevant happens. There is no polling budget to manage.
Price comparison
| Inoreader Pro | AyeWatch paid plans | |
|---|---|---|
| Monthly price | $9.99 ($7.50 billed yearly) | From $9 |
| API | Yes, 100 requests/day per zone | REST API for topics |
| Push to your code | No, you poll | Signed webhooks |
| MCP | Not listed | Yes |
| Filtering | Rules and filters you maintain | AI judges each item by meaning |
The last row is the one that saves engineering time. With AyeWatch, the relevance check happens before anything reaches your endpoint, and the payload already contains a summary, so your handler can stay a few lines long. Plan details are on the AyeWatch pricing page.
When the Inoreader API is still the right call
If you are building a reader client, syncing a user's subscriptions, or need the full stream of every article from a feed list, Inoreader's API is designed for that and AyeWatch is not. AyeWatch does not expose a raw article stream; it sends matches.
A practical split for developer tools
- Keep Inoreader, or any reader, for reading.
- Move the "wake me up" topics to AyeWatch: dependency deprecations, pricing changes on tools you pay for, security advisories.
- Verify the webhook signature in a small handler and post to your team chat or issue tracker.
FAQ
How much does the Inoreader API cost? It is included with Pro at $7.50 a month billed yearly or $9.99 monthly, with default limits of 100 requests a day per zone. Higher limits need a custom quote.
Who can use the Inoreader API without Pro? Developers building publicly available apps for platforms Inoreader does not support. Everyone else needs Pro or a custom plan.
Does AyeWatch's free preview include the API? No. The REST API, webhooks and MCP server come with paid plans, starting with Pro at $9 a month.
Frequently asked questions
How much does the Inoreader API cost?
It is included with Pro at $7.50 a month billed annually or $9.99 monthly, with default limits of 100 requests a day per zone.
Does AyeWatch's free preview include the API?
No. The REST API, webhooks and MCP server come with paid plans, starting at $9 a month.
Sources
- Inoreader developer portalInoreader
- Inoreader API rate limitingInoreader
- Inoreader pricingInoreader
- AyeWatch pricingAyeWatch
- AyeWatch features and FAQAyeWatch

