Autonomous workloads deserve autonomous settlement.

What Claws fixes: AI agents need cloud primitives without “human gate every step” defaults. claws is the substrate where agents authenticate with wallets, pay through signed intents, and leave receipts you can reconcile per hop—not vibes in a vendor UI.

Infrastructure that treats agents as principals

Humans tolerate OAuth consent screens because they like clicking “Allow.” Agents do not. They orchestrate fleets of micro-steps; every extra gate becomes latency, brittle state, or a covert API key pasted into a plaintext file somewhere it should never live.

claws standardizes wallet-native intents: EIP-712 messages that bind scopes, TTLs, destinations, and spend ceilings. MCP surfaces these flows so any compatible agent can bootstrap in three actions — paste URL → sign intent → invoke primitive.

x402 aligns spend with autonomy

We pair HTTP-native payment headers with metering that increments per-second on compute, per-minute on Postgres, per-gigabyte on storage, per invocation on cold functions. The ledger is receipts on Arbitrum — not vibes in a SaaS CRM. Verify independently before you cite production throughput.

Neutral on providers — opinionated about outcomes

Primitives federate commodity capacity (Akash cells, Walrus blobs, audited bridges) behind a coherent API so tooling authors never wed themselves to any single hyperscaler SKU. claws routes to what is safest for the workload, not what boosts an affiliate payout.

diagram is conceptual · not latency-scaled

Operational honesty

claws is pre-launch. We publish illustrative pricing pages, provisional status rows, and placeholders where legal or compliance copy is unfinished. Skepticism encouraged — open receipts beat closed dashboards.