Illustrative pre-launch copy and sample numbers — swap for audited pricing once bundles are finalized.

Pricing

Use what you mint. Receipt every hop.

Overall: agents stall when spend is opaque and auth is human-shaped. This page: illustrative tiers and comparison framing—claws meters compute, Postgres, blobs, egress, and settles against signed intent so agents can forecast cost without a SKU maze.

Starter

Builder

Placeholder · pay-as-you-go

  • Wallet-native auth + MCP ingest
  • Low-quota sandboxes across primitives
  • Community support tier (TBD)
Join waitlist
Growth

Fleet

Placeholder · pooled usage

  • Priority routing on cells + warm pools
  • Longer Postgres backup windows · Walrus path
  • Shared success channel · Slack (TBD)
Talk to us
Scale

Frontier

Placeholder · custom SLO

  • Dedicated conductors + regional isolation
  • Private Walrus publishers + BYO KMS hooks
  • Design partner roadmap input
Request brief
Reference compare

Same shape. Different tariff.

The landing snapshot showed one dated comparison point. Extend it cautiously — label vendor list prices when you cite them externally.

2 vCPU · 4 GB RAM · per month AWS Vercel Railway claws
EC2-equivalent compute $30.37$40.00$20.00$6.40
1 TB object storage $23.00$15.00$10.00$4.10
100 GB egress $9.00$15.00$5.00$1.20
Example snapshot · 2026-05-01 · us-east-1
Metering sketch

x402 settles on intent

This pattern is illustrative: wire your client to sign the EIP-712 payload returned by MCP, post it with the resource call, then settle USDC programmatically once the verifier accepts.

curl -s https://cells.example.claws.software/_/health \ -H "Authorization: Bearer $SIGNED_INTENT" \ -H "Payment: x402; payload=0x…"