Limits, pricing, and what is not built yet
The deployed limits and availability, followed by work that remains planned.
Last verified against production: . See current limits and availability.
Current limits
| Area | Current production behavior |
|---|---|
| Initial grant | 3 build credits once, at the first eligible build attempt. Eligibility checks wallet activity or balance on Robinhood Chain. |
| Build cost | 1 Fletch credit per platform build; 0 with your own model key. Provider API charges still apply. |
| Execution | 2 simultaneous build slots, additional accepted runs queued. The current agent-turn timeout is 45 minutes. |
| Prompt | 24,000 characters; five text files, 64 KiB each and 128 KiB total. |
| Images | PNG/JPEG with a vision-capable selected model: three images, 2 MiB each, 4 MiB total, 4096px per side, 16 megapixels. |
| Watch | 5 watchers per account, 1 new-pool watcher, 500 platform-wide. |
| RPC | 200,000 calls per day under the shared watcher/indexer ceiling; workers have separate sub-budgets. |
| Public API | 120 anonymous registry reads per minute per IP. Keyed requests: 600 per hour per key. |
| Webhooks | 5 endpoints per account, 10s delivery timeout and up to 8 attempts. |
Payment and deployment availability
The production checkout treasury is not configured, so credit checkout is unavailable. The $19 Builder subscription and FLETCH payment and burn terms shown on the landing page describe a planned offer. The backend currently implements the per-build credit rules above. The landing page's 10-credit offer differs from the deployed initial grant of 3; the grant in this table is what the backend applies.
Contract deployment currently targets Robinhood Chain testnet, 46630. Mainnet deployment is disabled. Watch is free during beta. A failed charged build receives its Fletch credit refund as a separate ledger entry. No Fletch refund can reverse a provider's own API charges.
The deployed wallet foundation supports compatible injected EVM wallets. The production Reown project ID is currently absent, so QR WalletConnect pairing is unavailable until it is configured. Hosted model keys use server-side encryption and decryption; server operators can access them.
Planned
- Small, medium and large build pricing, estimated costs, user-approved maximum budgets and admin price controls.
- Durable multi-hour execution, automatic conversation compaction, restart-resumable workers and off-host workspace restoration. Current browser reconnect and retained source files cover only part of that work.
- Complete historical swap coverage and exact rolling USD volume for the top active pools. Recent swap coverage and state sampling remain visible per pool while this work continues.
- Verified quote-token pricing coverage, market capitalization after burn balances, depth-integrity checks and the remaining Markets acceptance cases.
- Bridged and verified Ondo trust stamps backed by their required issuer and escrow evidence.
- The Builder subscription, recurring rollover credits, FLETCH checkout and burn, customer domains, expanded watcher caps and repository export as a plan entitlement.
- Team workspaces, dedicated capacity, Slack and email alerts, x402 payments and an npm-published MCP package.
Check the current reading
A healthy web response does not establish complete data coverage. The status page reports worker freshness and historical checkpoints. Real Telegram delivery, wallet signing and full app behavior require their own end-to-end tests; a documentation page loading successfully proves only that page's availability.