Docs

MoonX, PayBox, and x402 for people who still have email.

Connect

three rails. one human gateway. try not to merge them into a single confused blob.

stack map

flowchart TD
  human[Human with email]
  moonx[MoonX auth + passkey wallet]
  k4d[k4d products]
  agent[Agent host]
  paybox[PayBox MCP + grants]
  x402[x402 HTTP 402 sellers]

  human --> moonx
  moonx --> k4d
  k4d --> escrow[Escrow]
  k4d --> pay[Pay tip links]
  k4d --> sign[Sign walls]
  human --> paybox
  agent --> paybox
  paybox --> x402
  agent --> x402
  paybox -.->|optional fund| escrow

start here if...

you are...start
shipping a human app with walletspasskey-app / moonx
giving an agent spend authorityagent-pays-via-paybox / paybox
monetizing an HTTP API per callx402-paywalled-api / x402
doing a two-party deal UIescrow-with-agent-funding
tipping to unlock contenttip-link-unlock

relationships

  • moonx session authenticates humans in k4d UIs and unlocks embedded wallets.
  • paybox grants authorize agents without handing them keys.
  • x402 headers authorize access to a resource after payment, independent of k4d cookies.
  • k4d is composition + UX. official APIs remain normative upstream.

autonomous agentic commerce

until recently, agents hit a payment glass: they could research and write, then freeze the moment money was required. paybox + moonx passkey/MPC + x402 + MCP hosts remove that glass without handing the agent a raw key.

layerjob
x402HTTP-native pay-per-request (micropayments that card rails cannot do)
payboxcontrol plane: limits, allowlists, scoped outputs, audit
moonxpasskey circuit breaker + MPC signing for humans and step-up
MCPhow agents discover and call tools (including paid ones) inside cursor / claude / chatgpt / custom hosts

what becomes buildable:

1. zero-subscription data & research

agents pay per request in the background. an "omni-researcher" in claude or cursor can hit paywalled journals and premium APIs, settle micro-amounts via x402 + paybox, and stay inside a pre-approved budget. card rails with fixed fees make sub-cent / few-cent calls uneconomic; usdc on cheap chains does not.

2. autonomous cloud & infra arbitrage

a nomad workload agent compares rates, migrates jobs, pays decentralized compute per-second over x402, and tears down when done. treasury sets paybox limits ("$500/day on compute"); moonx passkeys are the breaker above that.

3. agent-to-agent micro-economies

a contractor agent hires a ui agent for $5, which hires a qa agent for $0.50. mcp is how they talk; x402 is how they settle; paybox is the wallet policy layer.

4. high-friction concierge (fire-and-forget)

"get me to tokyo by tuesday, $2000 budget." the agent plans flights and hotels, then paybox pauses above the autonomous threshold. you review on your phone, pass faceid / webauthn, moonx mpc signs, the agent finishes. cryptographic consent without pasting cards into chat.

read/write was yesterday. read/write/transact is the point.

recipes: agent-pays-via-paybox · x402-paywalled-api. deeper protocol playbook: install skills (x402-everything, paybox-everything).

tagline alignment

moonx = the keys · paybox = AI uses the keys · k4d = humans use the keys · x402 = pay-per-request rails.

the heat death of the universe is still on schedule. at least the architecture is coherent.