Pricing
A plan changes how much you can call, what operational tooling you get, and how quickly you can reach a human. It does not change a single field in the response. That is a deliberate product decision, and it is the reason this page can be short.
$66
For a single integration that needs a dependable read quota and per-key analytics.
$335
For teams running the API in production across several keys and environments.
Custom
For bulk and partner integrations that need contracted volume and named support.
Comparison
Seven rows at the top are identical on every plan. Everything that differs is quota, operational tooling, or support — never content.
| Capability | Starter | Professional | Enterprise |
|---|---|---|---|
| All eight REST endpoints | yes | yes | yes |
| MCP tools and resources | yes | yes | yes |
| Retained cleaned article bodies | yes | yes | yes |
| Source lineage and provenance fields | yes | yes | yes |
| Identical response shape on every plan | yes | yes | yes |
| Rate-limit headers on every response | yes | yes | yes |
| Per-key usage analytics | yes | yes | yes |
| Webhook subscriptions | no | yes | yes |
| Key rotation across environments | no | yes | yes |
| Higher rate-limit ceiling | no | yes | yes |
| Priority email support | no | yes | yes |
| Reserved capacity | no | no | yes |
| Custom source and category configuration | no | no | yes |
| Dedicated support and SLA | no | no | yes |
Anonymous read access sits underneath every plan and stays available. It is throttled per IP rather than per key, which makes it the right choice for evaluation and the wrong one for production traffic.
How limits work
A 429 is not a mystery. Every response states the caller's resolved tier and remaining quota, so a client can back off before it is refused.
| Tier | Who | Throttled |
|---|---|---|
| public | Anonymous callers | yes |
| registered | Developers with an API key | yes |
| enterprise | Bulk and partner integrations | yes |
Ceilings are configuration, not constants baked into this page. Treat the live rate-limit headers as authoritative.
Starter, Professional, and Enterprise receive the same fields, the same provenance, and the same retained bodies. What changes is quota, operations, and support — never the content shape.
A throttled anonymous tier remains available for evaluation, so you can verify the data before you commit to a plan. Paid plans add headroom and operational tooling on top of it.
Every response states the caller’s tier and remaining quota. A 429 always carries Retry-After, and each tier’s ceiling is documented rather than left to be reverse-engineered.
API keys are stored so that they cannot be read back. The console shows a short prefix, and shows the full value exactly once, at creation time.
Enterprise
Reserved ceilings, custom source and category configuration, aggregate benefit reporting, and a dedicated support and SLA agreement are arranged with us rather than self-served.
Your rate-limit ceiling is reserved and configured for your account, sized against the traffic you actually expect rather than a shared pool.
Source and category configuration is tuned to the domains that matter to you, so your team filters less and trusts more of what arrives.
Named support with an agreed response-time commitment, plus aggregate benefit reporting for the integrations that feed your reporting stack.
Questions
Anonymous read access returns the same record as any plan. Move to Starter or Professional when you need usage analytics, webhooks, and a higher ceiling.