Agent-First Pay Blog
Updates, deep-dives, and release notes for Agent-First Pay.
Design
Release notes
Agent-First Pay v0.10.0: An Outage Is Not Consent
When every provider's quote failed, the send confirmation printed 'skipping confirmation' and returned true — the payment went out having asked nobody. That, a rounding bias that made split payments free against the global cap, and an allowlist that let one configured category start a wide-open public daemon. Plus gRPC and its hand-rolled crypto layer are gone, replaced by a resource API with an OpenAPI face.
ReleaseAgent-First Pay v0.9.0: Illegal Commands Stopped Existing
v0.9.0 compiles the whole afpay CLI from a closed-world registry: one root, 27 command groups, 89 leaves, generated from a table rather than written out five times. Rules that used to be runtime checks — 'this credential is required for that backend', 'this listener flag belongs to that mode' — are now shapes, so an agent reads the requirement out of the help instead of discovering it by failing. Discovery answers cli-help-v2 JSON, scoped per command and bounded in size; bare --version answers a version event. Arguments become command-local, several aliases are gone, and the container image finally catches up to phoenixd 0.9.0 and Bitcoin Core 31.1 — including a signet path that never actually started.
ReleaseAgent-First Pay v0.8.0: Retry Without Paying Twice
v0.8.0 rebuilds afpay around the one question an autonomous payer cannot answer for itself: 'did that send go through?' An agent-supplied idempotency key makes a resend replay the first result instead of paying again; spend reservations hold the money in flight and expose reservation_ids for later reconciliation; EVM chain_id and Solana cluster are pinned at send time and fail closed on mismatch; and structured errors carry retry_after_ms so an agent can pace its own backoff. Underneath, the runtime is reorganized into six modes — cli, pipe, interactive, tui, rpc, rest — that all answer the same code-tagged protocol, and every one can be asked for its own schema.
ReleaseAgent-First Pay v0.7: Payment Tools Joined Agent-First Kit
The v0.7 release moved afpay into Agent-First Kit, hardened security and remote flows, kept backup/TUI work, and refreshed major wallet dependencies.
ReleaseAgent-First Pay v0.6: Wallet Operations Got a TUI and Backups
The v0.6 release added a full-screen wallet TUI, backup/restore commands, copyable payment artifacts, and a modular runtime shared across modes.
ReleaseAgent-First Pay v0.4.2: Solana Payments Became Order-Bound
The v0.4.2 update added Solana reference key support so agents can bind send and receive flows to a specific order or intent.
ReleaseAgent-First Pay v0.4: Security Became Part of the Runtime
The v0.4 release tightened REST security, standard wallet compatibility, rate limits, FX freshness, provider fallback, and wallet storage.
ReleaseAgent-First Pay v0.2: Settlement IDs Became Real
The v0.2 release made receive --wait flows return real on-chain transaction IDs and improved reproducible self-hosted payment deployments.
ReleaseAgent-First Pay v0.1: Multi-Chain Payments for AI Agents
The first Agent-First Pay release line: a single agent-oriented payment interface that spans Cashu, Lightning, Solana, EVM, and Bitcoin with spend limits and JSONL output.