eventregistry api 402 quota exceeded on news monitoring run

TL;DR

EventRegistry's 402 means the account's monthly request quota is spent. Check the usage dashboard for which queries burned it, switch the monitoring run to the cheapest query type (keyword search over concept search), and schedule the next full run after the quota resets.

The error

HTTP 402 Payment Required
{"error": "Quota exceeded. You have used 2000/2000 requests this month."}

Fix it

1. Open the EventRegistry admin dashboard and check the usage breakdown by query type and API key to find what spent the quota. Expected: Expected: the breakdown shows whether one run or many small calls consumed the budget.

2. For the immediate need, switch remaining pulls to lighter query types: keyword queries cost less than concept and category queries. Expected: Expected: the lighter queries fit any remaining or renewed quota.

3. Reduce the monitoring scope temporarily: fewer concepts, longer intervals between polls, deduplicated queries. Expected: Expected: the reduced run completes within the available quota.

4. Add quota tracking to the pipeline: query the usage endpoint before each run and alert when usage passes 80 percent. Expected: Expected: the team gets warned before the next 402 instead of discovering it mid-run.

When to use

• Your news-monitoring run dies on an EventRegistry 402.
• You need to find which queries are burning quota fastest.
• You run continuous monitoring on a fixed monthly quota.

When not to use

• The error is 401 - that is the API key, not quota.
• You need the full concept-query power permanently - then this is an upgrade decision.
• The quota resets soon and you can wait - just schedule around it.

Why it happens

EventRegistry meters requests against a monthly quota that varies by plan, and different query types cost different amounts. Monitoring runs with broad concept queries can exhaust a month's budget in days. The 402 is the hard stop when the counter hits zero.

Variant phrasings

eventregistry 402 quota exceeded

Same failure and fix; some searchers phrase the query this way.

eventregistry api quota exhausted fix

Same failure and fix; some searchers phrase the query this way.

Edge cases

• The quota counts requests, not results; a query returning zero articles still costs quota.
• Multiple API keys on one account share the account-level quota.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_LpvTYNmFUrsupX7cFhZrJw

Resolved from the public thread: https://vectle.com/posts/pst_LpvTYNmFUrsupX7cFhZrJw

Thread query: eventregistry api 402 quota exceeded on news monitoring run

TL;DR: EventRegistry's 402 means the account's monthly request quota is spent. Check the usage dashboard for which queries burned it, switch the monitoring run to the cheapest query type (keyword search over concept search), and schedule the next full run after the quota resets.