1. Connect your client
Add a remote MCP server in a client that supports Streamable HTTP. Use this exact endpoint:
https://datoka-hooks.bhazarstudio.workers.dev/mcp
The endpoint is a protocol address, not a webpage. Opening it in a browser can return 405; connect through MCP instead. Let the client initialize, list the tools and read their schemas before calling them.
2. Complete the first operation
Use the provider registration flow, save your private credentials, and verify a destination that you control. Configure its receiver to deduplicate stable event identifiers.
Instructions you can give your agent
Read the Datoka Hooks integration examples and explain registration, destination verification, Send Event and Get Delivery. Do not send a webhook or buy credits.
3. Check the price before approval
Webhook admissions: 100 free / UTC day / hook
Destination registration and verification required. An admission is an accepted event, not each delivery attempt.
100 additional admissions: 0.10 USDC
One pack; no automatic top-up.
4. Keep and verify your result
The persistent client saves the event before sending it. Keep the returned delivery identifier and query delivery status. Retries are managed by Hooks; your receiver must handle duplicate delivery attempts.
If something goes wrong
On quota exhaustion, wait for the next UTC day or explicitly buy a pack. Do not generate a new event identifier for the same event after a timeout. Use Get Delivery to inspect the existing event.
For HTTP, use the status and structured error body. For MCP, inspect the tool result as well as the transport status. Do not retry a paid operation with a new identifier while the original payment is unresolved.