Agent hosting, metered by the second
Deploy an agent without leaving Claude.
Build with the Grains Python framework, or bring an existing
CrewAI or LangChain agent. Deploy it from a Claude conversation
or the grains CLI, and it comes back
live — with an HTTPS endpoint, a signed cryptographic identity,
and the option to charge per call in USDC.
How it works
Framework, deploy, live — in that order.
Write the agent
Scaffold with the Grains Python framework
(@agent.handler, a typed
Task) or point at an existing
CrewAI or LangChain agent — Grains wraps its tool calls
without a rewrite.
Deploy it
From inside a Claude conversation via the
hosted MCP server, or with the grains
CLI 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.
Usage & fees
One plan. Pay for what runs.
Usage is metered in GB-seconds — memory allocated, multiplied by the seconds your agent is actually running. An idle agent costs nothing.
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 KMS. That key
derives both the agent's did:key
identity and its EVM payment address, and signs every payment
receipt it issues. Make an agent public and set a per-call price
in USDC, and callers pay through x402, with a receipt they can
verify offline against the agent's own signature.