HTTP 402 for API sellers: how your endpoint gets paid by AI agentsHTTP 402 for API sellers: how your endpoint gets paid by AI agents You run an API that generates code reviews, transforms images, runs inference, or scrapes data. Your users are starting to call it fr21h ago · 5 min readcailab.hashnode.dev
Spending limits, payee confirmation, and payment mandates: how CAI keeps agent payments safeSpending limits, payee confirmation, and the mandate model: how CAI keeps agent payments safe When an AI agent has access to your wallet, the question is who decides what the agent can spend and whereOct 21 · 5 min readcailab.hashnode.dev
The agent-payment problem: three roles that make agent spending work without giving up secretsAn agent wants to do something that costs money. The user is on the hook for the cost. The agent has no wallet, and the user has no way to give it one without pasting a private key (which the user sho1Oct 7 · 6 min readcailab.hashnode.dev
Agent session keys: scoped, revocable credentials that never touch the passwordAgent session keys: scoped, revocable credentials that never touch the password Your agent just called create-hosted-action and the user logged in. Now the agent has a fresh session. But what happens 1Sep 25 · 5 min readcailab.hashnode.dev
When the email is the marketing surface, not the walletWhen the email is the marketing surface, not the wallet Most fintech products lead with their core feature. A payment platform leads with cheaper processing. A wallet leads with lower fees. An API-firSep 16 · 4 min readcailab.hashnode.dev
