agent-native cloud services

Cloud infrastructure that agents pay for themselves.

No accounts, no API keys, no signup. Your agent authenticates and pays with its wallet — per request, in USDC over x402 — and every value is encrypted client-side. Zero-knowledge by default.

npx @agentkv/cli set memory:goal '{"task":"ship"}'

How it works

An agent pays for exactly what it uses, in the same round-trip as the request — no setup, no API keys, nothing stored in the clear.

  1. GET /kv/memory:goal Signed by the agent's wallet. No API key, no account.
  2. 402 Payment Required · $0.001 A price, quoted per request.
  3. x402 payment · USDC Signed by the same wallet, settled on-chain.
  4. 200 OK · encrypted value Readable only by the agent that wrote it.
  • Wallet is identity

    The agent is known by its signature. Nothing to provision, nothing to leak.

  • Pay per request

    Settled in USDC over x402, or drawn from pre-paid credits. You pay for exactly what you use.

  • Zero-knowledge

    Values are encrypted client-side before they leave. The service stores ciphertext it can't read.

AgentKV

An encrypted key-value store your agents use in three lines — the model above, running as a service. Wallet-authenticated, paid per request, zero-knowledge.

Encryption
AES-256-GCM, client-side
Pricing
$0.005 write · $0.001 read, or pre-paid credits
Values
up to 256 KB, with TTL
Explore AgentKV →
npm i -g @agentkv/cli # or: npx @agentkv/cli
export AGENTKV_PRIVATE_KEY=0x… # your agent's wallet
export AGENTKV_ENDPOINT=https://… # your AgentKV endpoint

agentkv set memory:goal '{"task":"ship"}' # encrypted, paid per write
agentkv get memory:goal # decrypted client-side

A proponent of x402 — not just a vendor of it.

x402 is an open protocol with a growing ecosystem. We build on it, contribute to it, and point you to the best of it — even when that's not us.