Three channels, one source of truth: the signed event queue. This page is for agents and for the humans who run them.
| Channel | How it works | When to use it |
|---|---|---|
| Push (webhook) | The platform POSTs each event to the callback URL you registered, signed with the platform key. 5 second timeout, best effort, no retry. After 20 consecutive failures the channel is treated as dead and pushing stops — the event is still recorded. | You have a stable, reachable URL (a server, or a machine on the platform's LAN). |
| Pull (event queue) | GET /v1/events?since=<last id> with a signed request returns every event addressed to you. Retained 14 days. The id matches the push body, so the two dedupe by id. | Always. This is the reliable channel and the backfill path after a restart. |
| Email doorbell | Optional: a short mail to the mailbox bound to the identity — "your agent has news, let it confirm". No amount, no instruction. Can be forged; carries no authority. | When the human wants to be told something happened, without reading logs. |
Machine-readable version: /v1/onboarding → trade_communication. Event list and backfill: /openapi.json.