Three wallets, email delivery, and one-hour latency are enough to validate the product without giving away a production ops tier.
0watch pricing
Price by monitored blast radius, not by generic SaaS seat count.
0watch pricing is built around the points where agent operators actually feel pain: wallet count, alert latency, delivery channels, and history depth. Free proves the signal. Developer gets a solo builder into production. Team covers the shared ops surface. Enterprise starts when contracts or wallet fleets force it.
$49
Developer lands on the market-standard entry price for production alerting.
$199
Team is the expansion tier for multi-wallet ops and shared response loops.
3 wallets
Free is intentionally capped so real deployments convert quickly.
Feature Highlights
Each tier is optimized for a different operator shape.
The packaging follows the pricing research and the actual signup flow already live on 0agent.ai.
Ten wallets, webhook delivery, Slack support, and real-time alerts cover the first serious deployment without a sales call.
Fifty wallets, PagerDuty and Telegram, multi-user access, and a one-year history window fit the first real operator team.
Use Enterprise when you need higher-volume fleets, custom SLAs, compliance work, or dedicated rollout support.
Plans
Buy the tier that matches the amount of capital and coordination you are protecting.
Developer is the self-serve default. Team is for shared production operations. Enterprise is intentionally contact-led.
Evaluate
Free
$0/mo
3 wallets · 1 hour latency · email only
- 7 days of transaction history.
- Read-only API at 60 requests per minute.
- Best for demos, first API calls, and internal validation.
Conversion pressure comes from wallet count, webhook access, and latency.
Recommended
Developer
$49/mo
10 wallets · real-time alerts · Slack + webhook
- 90 days of history and full CRUD API access.
- Webhook signing and 300 requests per minute.
- Built for solo builders or small teams shipping on-chain agents.
This is the first paid tier because it matches the market floor and the typical self-serve buying motion.
Operate
Team
$199/mo
50 wallets · PagerDuty + Telegram · multi-user
- One year of history and 1,000 requests per minute.
- Up to 10 seats with a 24-hour support SLA.
- Best for startups, funds, and protocols running multi-wallet systems.
This tier is designed to absorb the first real shared ops loop before enterprise requirements show up.
Contract
Enterprise
Customstarting at $1k+
100+ wallets · SLA terms · custom rollout
- Custom latency, retention, and support targets.
- Multi-tenant, compliance, and dedicated infrastructure options.
- Designed for institutional operators and platform-scale fleets.
Enterprise starts when overages, contracts, or compliance work make self-serve the wrong fit.
Feature Comparison
Use the table to choose the smallest tier that still protects your production loop.
The differences that matter are delivery channel, latency, wallet capacity, and how much historical context the operator keeps.
| Feature | Free | Developer | Team | Enterprise |
|---|---|---|---|---|
| Wallets | 3 | 10 | 50 | 100+ / custom |
| Alert latency | 1 hour | < 5 min | < 5 min | < 2 min or custom |
| Delivery channels | Email, Slack, Webhook | Email, Slack, Webhook, PagerDuty, Telegram | Custom routing and escalation | |
| History window | 7 days | 90 days | 1 year | Custom retention |
| API access | Read-only, 60 req/min | Full CRUD, 300 req/min | Full CRUD, 1,000 req/min | Custom limits |
| Support | Docs only | Community/docs | Email with 24h SLA | Named support and negotiated SLA |
| Best fit | First evaluation | Solo builder or small team | Shared production ops | Institutional or platform deployment |
FAQ
Common pricing questions.
The goal is to make the upgrade path explicit before a team hits a wall in production.
Why is Free capped at three wallets?
Because anything larger starts to look like a real deployment. The free tier is for evaluating signal quality, not for silently running production ops.
Why is Developer the first paid tier?
$49 is the market-standard entry point for developer tooling with real production value, and it keeps self-serve checkout simple.
When should a team upgrade to Team?
When multiple people need the same alert stream, more channels matter, or the monitored wallet count goes beyond the first serious deployment.
What pushes a customer into Enterprise?
Enterprise is for contract requirements: higher-volume fleets, stricter SLAs, multi-tenancy, compliance, or custom retention and delivery behavior.