Account setup
Create the account context the API expects.
0watch uses an account id plus API key. This form keeps that state in the browser so the paid flow can return cleanly on the success page.
0watch signup flow
Start free in-browser, route Developer through Base payments, and stage Team plus Enterprise through rollout.
Sign up, add your first wallet or contract address, and receive your first alert in under 5 minutes. This path now matches the crypto-native packaging: free evaluation in-browser, Developer payment requests on Base, and Team or Enterprise routed into the staged waitlist flow until backend packaging expands.
Free starts instantly
Developer pays on Base
Team and Enterprise stay human-routed
Tier selection
Pick the path by wallet count, alert urgency, and rollout model.
The selected tier controls whether the button issues a key directly, creates a Base payment request against /api/billing/checkout, or sends you to the staged waitlist/contact path.
What the browser is about to do
Signup, checkout, key issuance, then dashboard.
Selected tier
Free
Checkout mode
n/a
Last success URL
pending
Next after signup
Add the first wallet and inspect the feed.
POST /api/wallets {"address":"0xYourWalletAddress","label":"prod-agent"}
Step 1
Wallet registry
Register one wallet and label it so the dashboard is readable the first time you land there.
Step 2
Live dashboard
Open the dashboard route and confirm balances, recent transactions, alert counts, and delivery health.
Step 3
Webhook coverage
Point high-severity alerts at Slack, Telegram, or your incident endpoint before the wallet moves serious capital.
API key
Keep the issued key close.
Issued key
Use this as the X-API-Key header when calling the 0watch API directly.
No key issued yet. Free tier generates it immediately. Paid tiers generate it on the billing success page after checkout completes.
USDC on Base is the default rail. The payment page can switch to an ETH quote if needed.
Docs
Keep the deeper references one click away.
The browser path handles the first-run flow. The docs cover the full API surface, webhook payloads, and the operational details once the service is live.