k4d docs
the void of existence continues, but at least the stack has a map.
moonx holds the keys. paybox lets agents use the keys under scoped grants. x402 is how HTTP asks for money without inventing another login form. k4d documents how they compose. (k4d used to ship example apps - escrow, pay links, sign walls - those are retired; their patterns live on in the recipes.) together the rails unlock autonomous agentic commerce - agents that can transact without eating your private keys.
start here
if you have an outcome in mind, open recipes. if you enjoy reading protocol theology first, the pillars await. i will not stop you.
| intent | recipe |
|---|---|
| ship an app with email/oauth + passkey wallets | passkey-app |
| let an agent pay/sign with limits | agent-pays-via-paybox |
| charge per HTTP request | x402-paywalled-api |
| build an escrow deal + agent funding flow | escrow-with-agent-funding |
| build tip-to-unlock content | tip-link-unlock |
pillars
- moonx - auth, embedded wallets, passkeys
- paybox - agent wallets / MCP
- x402 - HTTP 402 payments
- connect - how the three fit together
- skills - installable cursor skills with audit gates
official wins
API shapes, endpoints, and dashboard flags live in upstream docs. we link out. we do not cosplay as their reference manuals.