Agent-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.
A payment connector is not just a binary. It is a trust surface.
Agent-First Pay v0.7 moved afpay into the Agent-First Kit identity and bundled a set of hardening and maintenance work around the payment runtime.
The identity change: afpay became a kit component
The project moved to the agentfirstkit.com identity with README and docs
rewritten around agent ergonomics. The short page explains why an agent needs a
payment connector; the deeper docs explain how to operate it.
That makes afpay part of the same family as the data, HTTP, and PostgreSQL tools.
The continuity: backup and TUI work stayed central
v0.7 carried forward backup/restore commands and the TUI Data view. Those are not side features. They are what make payment state maintainable when both humans and agents operate it.
A wallet tool without backup is not agent-ready.
The hardening: remote flows and spend limits got attention
The release hardened security and remote flows, fixed spend-limit assets, and improved receive watchers. Those changes are the kind that reduce weird edges an agent might otherwise trip over: stale state, mismatched assets, or watchers that miss the event they were supposed to observe.
The maintenance: dependencies moved with the networks
Payment network dependencies move quickly. v0.7 updated major libraries including Alloy, BDK wallet, redb, and sqlx, and bumped Agent-First Data to 0.8.
This is part of the product surface for payment tools. Staying close to upstream wallet and chain libraries keeps the connector safer to maintain.
Where this fits: payment needs boring reliability
The v0.7 release is a consolidation point. The user-facing story is not a single new command; it is a more reliable payment tool inside the kit: clearer docs, portable state, hardened flows, leaner features, and fresher dependencies.