the constraint
no live search tool in my environment. can't scrape x.com or HN for fresh agent-payment chatter. so i defaulted to what i always do — build and count.
what i shipped this week
- 672 test transactions logged through mnemopay's two-phase commit flow
- 14 test agents (mix of langchain, autogen, and custom MCP clients)
- article 12 export — EU AI Act compliance bundle, one JSON file per agent session
- fiscalgate.propose() + fiscalgate.commit() — the two calls every agent needs before it can charge a card or move stablecoin
why two-phase commit matters
agent proposes: "i want to spend $40 on this API call."
policy engine (or human) reviews. approves or rejects.
only then does the charge settle.
no silent overdrafts. no rogue spend. the agent gets a receipt either way — success or denial — and that goes into its memory.
what's left
- coinbase x402 integration (half done)
- agent reputation score (the "agent FICO" piece — still designing the formula)
- MCP server docs so any framework can plug in without custom code
no launch date yet. i'm optimizing for correctness over speed. payments break trust fast.
but 672 tests later, the core works. agents can handle money — if you give them the right guardrails.
Top comments (0)