Back to Browse
PreReason Change Events Feed
x402
PreReason Change Events Feed is a paid API for AI agents from api.prereason.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-16).
Returns a paginated page of change events (briefing state changes, release publications, company figure updates, news) since a given cursor, optionally filtered by company addresses, event types, and news kinds.
Price / call$0.01
Success—
StatusUnknown
How this service works
What changed since your last read: one page of PreReason's change events after a cursor. A briefing's state label, a tracked release, and, for the companies you name (?companies=, at most 200), newer figures, a situation turning on or filed news (?kinds= narrows it). Each event says what changed, when it happened, when PreReason knew it and where to fetch it, never a value. With no cursor it answers the last 24 hours; each answer's next_cursor is where the next read starts.
Output
Returns a JSON object with an array of change events (each describing a state change, published release, updated company figures, or company news), a boolean has_more indicating if more pages exist, and a next_cursor string to use in the subsequent paginated request.
Example use cases
Earnings release alert for watchlist
“Pull any new earnings-release or material-event updates from PreReason for my company watchlist — addresses 0xABC123, 0xDEF456, 0xGHI789 — since cursor 1718500000, limit 25.”
Morning briefing state change digest
“Give me all state.changed and release.published events from PreReason since my last cursor 1718900000 so I can see which briefings changed status overnight.”
Leadership change monitoring
“Check PreReason for any leadership-change or ownership-report events for these 5 companies — 0x111, 0x222, 0x333, 0x444, 0x555 — starting from cursor 1719000000, and show me everything up to 100 results.”
Technical details
Endpoint
GEThttps://api.prereason.com/api/events?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need to poll for incremental changes — new events since a known point in time — across briefing states, company releases, and financial figures. It is the right choice when you are building a monitoring loop or change-detection pipeline for a set of tracked companies, rather than fetching a full snapshot of current data. The cursor-based pagination makes it suitable for reliable, stateless polling at regular intervals.
Side effects
- Invalid cursor format (must be 1-18 digits) returns a 400 error
- More than 200 company addresses in ?companies= parameter returns an error
- Invalid event type or news kind enum value causes a 400 bad request
- Empty events array returned if no changes occurred since the given cursor
- Payment not processed (402) if x402 micropayment header is missing or incorrect
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
Schema · Response
{
"type": "json",
"example": {
"events": [],
"has_more": false,
"next_cursor": "0"
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"