0watch API quickstart
Three calls to live wallet monitoring.
Prospects should be able to sign up, register a wallet, and arm a webhook without digging through the full docs set first. This page keeps the first five minutes visible and copyable.
Copy the exact commands you need.
The commands below come directly from the live 0watch onboarding flow and reference docs, trimmed to the first integration path that matters on a landing page.
1. Sign up
Get the first API key immediately.
curl -X POST https://watch.0agent.ai/api/auth/signup \
-H 'Content-Type: application/json' \
-d '{
"email": "you@example.com",
"password": "YourPassword123"
}'
2. Add wallet
Start monitoring the address you actually care about.
export API_KEY="owk_..."
curl -X POST https://watch.0agent.ai/api/wallets \
-H "Content-Type: application/json" \
-H "X-API-Key: $API_KEY" \
-d '{
"address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
"label": "treasury signer"
}'
3. Set webhook
Route high-value transfers into your own system.
curl -X POST https://watch.0agent.ai/api/webhooks \
-H "Content-Type: application/json" \
-H "X-API-Key: $API_KEY" \
-d '{
"url": "https://ops.example.com/0watch",
"wallet_address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
"threshold_eth": 0.1
}'
What this buys you in the first session
The page exists to answer the prospect question fast: why use 0watch instead of rolling a one-off listener and hoping it stays healthy?
- Signup returns a usable API key immediately instead of forcing a dashboard setup detour.
- Wallet registration is one authenticated call, so the monitored surface is explicit.
- Webhook setup turns the API into an operational signal path instead of a passive explorer.
Need the deeper path?
The quickstart is the fast lane. The rest of the docs stay one click away.
- Full API reference for endpoint coverage, error codes, and schemas.
- Webhook guide for signatures, Telegram, and delivery behavior.
- API explorer if you want to inspect public endpoints before signup.
Upgrade when the monitored surface gets real.
The quickstart converts on clarity, but the pricing block has to explain what changes once the operator moves beyond evaluation.
$0
5 wallets- 1,000 calls/day
- 7 days of history
- Webhook delivery included
$49/mo
10 wallets- 10,000 calls/day
- 90 days of history
- Built for live operator use
$199/mo
50 wallets- 50,000 calls/day
- 1 year of history
- Built for live operator use
Live signup
Browser flow that issues the first key and walks into wallet setup.
Open signupDocs home
Browse the rest of the 0watch docs set once the first integration is working.
Open docsPricing
Compare plans, checkout paths, and the crypto-native upgrade flow.
Review pricing