Honest comparison
KeyForge vs Vertically-Integrated Payment Stacks
A wave of agent-commerce platforms now bundle the payment rail, the settlement token, and the ledger into one owned stack: your agents pay through their pipe, in their unit, recorded in their books. KeyForge takes the opposite stance. Settlement is a standards-based, non-custodial layer (HTTP 402 plus x402, EIP-3009 stablecoin transfers) that runs on whichever rail you choose, or entirely inside your own infrastructure. We settle on any rail, are owned by none, and attest it cryptographically.
Where Vertically-Integrated Payment Stacks is strong
One-vendor convenience
A single SDK for identity, wallet, settlement, and reporting, genuinely fast to adopt if you are comfortable standing your agent economy up inside one company stack.
Managed custody
The vendor holds balances and moves funds for you, so there is no relayer, RPC, or key custody for you to operate, less to run on day one.
Built-in reconciliation
Because the vendor owns the ledger end to end, their dashboards reconcile cleanly against their own rail, tidy as long as you never need to leave it.
Where KeyForge wins
Settles on any rail, owned by none
x402 is an open HTTP-402 payment scheme, not a proprietary pipe. KeyForge presents a machine-readable payment challenge and settles against whatever stablecoin and network your policy allows. We take no position in the rail and hold no stake in which one you pick.
Non-custodial by construction
Payments move via EIP-3009 gasless transfer authorizations signed by the payer. KeyForge never takes custody of funds, a facilitator verifies and relays the payer own signed authorization. There is no KeyForge float to trust or to freeze.
Self-hostable settlement
Run the facilitator inside your own VPC or air-gapped environment. Settlement traffic, relayer keys, and RPC endpoints never leave your infrastructure, the sovereign counterpart to a vendor who insists funds flow through theirs.
Cryptographically attested
Every settlement, rejection, and over-cap challenge is sealed into the same HMAC hash-chained attestation ledger as the rest of KeyForge, plus optional W3C Verifiable-Credential spend mandates. You can prove what an agent was authorized to spend and what it actually settled, to an auditor who trusts neither of us.
Enforced allowlists and caps
Denominate a key spend cap in USD or a specific stablecoin and restrict which stablecoins it will ever accept. A payment offered on a rail or in an asset outside the allowlist is refused before any settlement is attempted.
Feature comparison
| Capability | Vertically-Integrated Payment Stacks | KeyForge |
|---|---|---|
| Rail ownership | Vendor owns the rail and token | Any rail, owned by none |
| Custody | Vendor holds and moves funds | Non-custodial, payer-signed EIP-3009 |
| Deployment | Vendor-hosted only | Hosted or self-hosted in your VPC |
| Standard | Proprietary SDK | Open HTTP 402 plus x402 |
| Proof | Vendor dashboard | HMAC-chained receipts plus VC mandates |
| Asset control | Vendor unit of account | Per-key stablecoin allowlist plus caps |
| Mainnet exposure | On by default | Testnet-first, mainnet double-gated |
Frequently asked
Give your agents keys that can’t leak
Start with 3 virtual keys and the full HMAC audit chain, free. Migrating from Vertically-Integrated Payment Stacks is a base-URL change.