# Track 1 — emit events to AO today

If your platform has no public API or webhook surface yet, you can
still integrate immediately: let your customers ingest your events via
an AO Webhook. Each AO customer can mint a webhook URL + secret inside
AO; you add an "Automated Operations" destination in your product that
POSTs events to it.

Contract:

- **Body**: JSON with `event_type` (`<your-ns>:<subkind>`, see the
  event taxonomy), `event_id` (unique per event), `occurred_at`
  (RFC 3339), and your payload fields.
- **Signature**: `hmac_sha256` over the raw body with the customer's
  AO-minted secret, hex-encoded, in an `X-Signature` header.
- **Retries**: retry non-2xx with backoff for 24h; redeliver with the
  same `event_id` so AO dedupes.

This gets billable, agent-visible data flowing for mutual customers
within days — and you can graduate to a first-class catalog tile by
building toward Track 2.