grains
Ship an agent
in one conversation.
Build it in Claude — or bring your CrewAI or LangChain agent — and deploy it without leaving the chat. It comes back live: signed identity, scale-to-zero endpoint, paid per call in USDC.
The whole deploy
This is the entire workflow.
How it works
Write the agent
A handler in Python or JavaScript with the Grains framework
(@agent.handler, a typed Task) — or point at an existing
CrewAI or LangChain agent. Grains wraps it without a rewrite.
Deploy it
From inside a Claude conversation via the hosted MCP server
(uvx grains-mcp), or grains deploy from a terminal.
Builds run scale-to-zero — you don't pay for an idle agent.
It comes back live
An HTTPS endpoint, a signed did:key identity minted in KMS, and —
if you set a price — a metered, x402-payable endpoint with offline-verifiable
receipts.
Identity & payment
Every agent signs its own work.
Each deployed agent gets a secp256k1 keypair held in AWS KMS —
sign-only custody; the private key never leaves the HSM. That key derives the
agent's did:key identity and its
payment address, and signs every receipt it issues. This one is real — generated
from the public test vectors, verifiable offline with
grains verify.
Pricing