# Datoka Hooks
> Public webhook relay for applications and AI agents. Signed relay observations, retries, encrypted pending bodies.
## Start
- Public MCP: https://datoka-hooks-test.bhazarstudio.workers.dev/mcp
- Guide: https://datoka-hooks-test.bhazarstudio.workers.dev/getting-started
- Download Python, JavaScript and MCP examples: https://datoka-hooks-test.bhazarstudio.workers.dev/examples
- HTTP/MCP recipes: https://datoka-hooks-test.bhazarstudio.workers.dev/integrations
- OpenAPI: https://datoka-hooks-test.bhazarstudio.workers.dev/openapi.json
- Live offer: https://datoka-hooks-test.bhazarstudio.workers.dev/pricing
- Health: https://datoka-hooks-test.bhazarstudio.workers.dev/health
## Fit
Use for job completion notifications, passing an agent result reference, or retrying a temporary receiver outage.
You need an HTTPS receiver you control and the ability to publish its ownership challenge. Hooks does not provide an email inbox or notification app.
## Workflow
1. Register a destination using a secret stable recoveryKey. Save returned credentials privately.
2. Publish the challenge and call verify_destination.
3. Call accept_hook_event with a stable eventId and exact serialized bytes.
4. On uncertainty retry the SAME eventId and bytes. Read get_hook_delivery and handle terminal failed explicitly.
5. Verify signed observations. Your receiver must verify the HMAC and deduplicate delivery IDs.
## Cost and authorization
100 new admissions per UTC day are free. Read /pricing for current optional prepaid credits.
Use get_hook_credits and purchase_hook_credits. A quote does not charge money.
Only buy within the owner's authorized budget. An EOA EIP-3009 wallet on Base is required; smart-wallet signatures are not supported.
On purchase uncertainty reuse the SAME purchaseId and signed payment. No automatic renewal.
Credits pay for additional admissions, not successful business processing. Retries do not spend extra credits.
## Boundaries
HTTP 202 means accepted; a receiver 2xx is an observation, not proof of business processing.
No exactly-once delivery guarantee. Public beta without a contractual uptime SLA.
Keep tokens, managementToken, recoveryKey, receiver URLs and payloads out of public prompts or logs.