Skyfire sells what AGIRAILS sells: a way for one AI agent to pay another for services, machine to machine. That makes this the head-on matchup of the category; Nevermined orchestrates human budgets and Google's AP2 standardizes authorization, but here both sides claim the same transaction. Two Ripple payments veterans founded Skyfire, Coinbase Ventures and a16z's CSX seeded it, and Experian, F5, and Fastly have wired its credentials into the enterprise edge.
The overlap ends at the trust model. Skyfire's answer to a risky machine counterparty is identity: verify the human behind the agent (KYA, Know Your Agent), hold everyone's balances on the platform, and let the seller deliver first and charge afterward. If something breaks, you know whose name is on the account. AGIRAILS' answer is structure: the buyer's USDC goes into a contract before work starts, the chain records the attested delivery, and the contract releases funds by rule.
The definition
Skyfire is a hosted identity and payments platform for AI agents, built by Skyfire Systems (founded 2023 by Ripple alumni Amir Sarhangi and Craig DeWitt). An agent gets an account with a wallet "managed by Skyfire," funded by card or USDC on Base (ACH and wire with a paid subscription); deposits become USD-denominated Credits on Skyfire's books. To pay, the buyer agent requests a short-lived signed token from Skyfire's API, hands it to the seller, and the seller charges the token after delivering; Skyfire then makes an internal transfer between its wallets. KYA, the identity layer, attaches a verified human or business to every agent and is recognized by edge networks including F5 and Fastly, and by Cloudflare through Experian's Agent Trust framework. The token protocol, KYAPay, is published as an open spec with an IETF draft.
AGIRAILS ships ACTP, the Agent Commerce Transaction Protocol, as contracts on Base. The escrow has two exits, and only two: to the provider once it attests delivery on-chain and the requester's dispute window closes without challenge, or back to the buyer by the rules of the eight-state lifecycle. The protocol asks nothing about who either agent is; identity (ERC-8004, the open agent-identity standard) is available for reputation, and the escrow does the protecting.
The Skyfire specifics on this page come from its developer documentation and Services Agreement; the links and verification date sit at the end.
Is AGIRAILS the same as Skyfire?
No. Skyfire onboards you to an account: platform wallet, Credits balance, identity verification, checkout APIs. AGIRAILS hands you a contract address: your agent holds its own USDC and transacts against public contracts with published rules. What differs is everything around the money: who holds it, when it moves, and what happens when the two sides disagree.
The comparison below is about those mechanics, not about which company executes better.
What is the difference between AGIRAILS and Skyfire?
Skyfire and AGIRAILS put their trust in different objects. Skyfire trusts the person it has verified. AGIRAILS trusts the contract holding the money.
The money is the sharpest split, so take it first. On Skyfire, deposits stop being crypto on arrival: USDC sent on Base lands as a USD balance, and balances live as Credits on Skyfire's internal ledger. The Services Agreement (§3.1) states that Credits are "non-refundable," are "not legal tender or currency of any kind," have "no cash value," and expire after a year unless law requires otherwise. If the account closes or is terminated for cause or breach, they "cannot be recovered." The agreement contains no withdrawal or redemption provision. Some of that reads like standard prepaid-balance boilerplate, and much of it is; gift cards carry similar terms. The difference is what sits behind the balance: for an autonomous agent, that ledger entry is its working capital. On AGIRAILS, the buyer's USDC stays USDC. It sits in a contract the operator cannot reach, and it comes back out the moment the state machine says so.
Second, the order of operations. A Skyfire seller delivers first, then charges the buyer's token up to the spending cap the buyer set on it; Skyfire's internal transfer follows. An AGIRAILS provider starts work with the funds already committed on-chain, and a requester pays only when delivery is proven.
Third, what happens when something goes wrong. Skyfire's recourse is the Verified Service Guarantee: the buyer emails support within five days of the charge. Only claims against Verified Sellers qualify, Skyfire decides at its sole discretion, and a successful claim is restored as Credits. Unverified sellers carry no reversal path. On AGIRAILS the path is defined before anyone needs it. A challenger stakes a bond on-chain, so a frivolous dispute costs real money; that part runs on mainnet today. The full court is part of the protocol's design: an ensemble of AI arbiters gives the opening ruling, and appeals stay bonded. UMA's optimistic oracle, a decentralized dispute layer used across DeFi, delivers the final ruling on-chain.
Fourth, identity itself. On Skyfire, identity is the product: KYA verification is run by Skyfire on a paid subscription, and the credential is a Skyfire-signed token. The docs describe no way to take verification status or history out of the account. On AGIRAILS, identity is optional and agent-owned: ERC-8004 registries live on a public chain, and the record accumulates to the agent rather than to an account at any company.
Side by side
| Criterion | AGIRAILS | Skyfire |
|---|---|---|
| Kind of thing | Settlement protocol, ACTP; Apache-2.0 contracts on Base | Hosted platform: KYA identity, managed wallets, checkout APIs |
| Trust model | Structural: escrow and a validated state machine | Identity: a verified human or business behind every agent |
| Where the money lives | USDC in an on-chain contract | USD Credits on Skyfire's internal ledger |
| What happens to deposits | Stay USDC; move only by contract rule | Become Credits: non-refundable, no cash value, expire per the terms |
| Order of operations | Funds committed on-chain, then work | Seller delivers, then charges a Skyfire-issued payment token |
| Settlement | On-chain, at the closing state transition | Internal ledger transfer between platform wallets |
| Escrow | Core of the protocol; funds locked before work | None; seller delivers first, then charges |
| Disputes | Bonded on-chain challenges today; the dispute court design ends at UMA's oracle | Verified Service Guarantee: 5-day email dispute, Verified Sellers only, sole discretion, restored as Credits |
| Agent identity | Optional; ERC-8004, owned by the agent | The product: KYA (KYB/KYC), Skyfire-issued, subscription-gated |
| Identity portability | Public registry; survives any vendor | Exit undocumented; status and history live in the Skyfire account |
| Access to bot-gated web | Not addressed | Strong: F5, Fastly, and Cloudflare via Experian's framework |
| Funding rails | USDC on Base | Card and USDC on Base for all users; ACH/wire with subscription |
| Fees | 1% per settlement with a $0.05 minimum; gas is sponsored | No fees in the terms today (buyer side); new fees possible on 30 days' notice; subscriptions gate KYA and ACH/wire |
Getting past bot walls, captchas, and 403s is a real problem. Skyfire addresses it; AGIRAILS does not.
What people conflate about AGIRAILS and Skyfire
"Skyfire runs on crypto rails." USDC goes in; Credits come out. Payments are internal transfers between Skyfire-managed wallets, and no transaction settles on-chain. The open KYAPay spec defines coin, card, and bank settlement types for future interoperability, but the platform today is a closed ledger with a crypto on-ramp. On ACTP the chain is the ledger: every settlement is a public Base transaction anyone can look up.
"KYAPay is open, so the stack is open." The spec is open by any standard: CC BY-SA license, an IETF Internet-Draft with an outside co-author, more standards work than most of the category has attempted. Operation is another matter. Tokens are issued and signed by app.skyfire.xyz, verification requires a Skyfire subscription, and Credits, status, and history live inside the Skyfire account with no documented way out. An open wire format around a proprietary operator is still a proprietary operator.
"A verified agent is a safe counterparty." Verification and escrow answer different stages of a failure. Identity tells you who to pursue after something goes wrong; it does nothing about the money at the moment things go wrong. On Skyfire that moment resolves at the platform's discretion, if the seller was Verified. On AGIRAILS it resolves by contract: the funds were never anywhere a counterparty, or an operator, could take them.
Do AGIRAILS and Skyfire compete?
Yes, more directly than any other pair in this series. Both sell agent-to-agent payments with no card and no human approving each transaction. Both court developers building buyer and seller agents, and each treats autonomous machine commerce as the product rather than a feature.
There is one seam where they compose instead. KYA solves access: an agent that has to get past an enterprise edge benefits from a credential those gatekeepers recognize. ACTP solves settlement: where the funds go once the two agents agree. An agent could present KYA at the door and settle the work in escrow, because identity at the edge and structure at the settlement layer answer different questions.
Is AGIRAILS a Skyfire alternative for agent-to-agent payments?
Yes, and the choice is a clean trust-model decision. Pick the identity model when knowing your counterparty is the protection you need: established sellers, an enterprise compliance requirement, a platform relationship you expect to keep. Pick the structural model when the protection has to hold against unknown counterparties, when payment must depend on delivery rather than on reputation, or when the funds should never sit on any company's books, including ours. Skyfire asks you to trust Skyfire, and gives you real reasons to. AGIRAILS is built so the question does not come up.
When should I use AGIRAILS instead of Skyfire?
If your problem is access, Skyfire solves it. If your problem is what happens to the money, AGIRAILS does.
Choose Skyfire if:
- your agents keep hitting bot walls and you need a credential the enterprise edge recognizes
- compliance requires a verified human or business identity (KYB/KYC) attached to every agent you run
- you want to fund agents with a card or bank transfer and never touch crypto operations
- the services you are buying already live in Skyfire's network (Apify, Dappier, Getty Images, Reuters, and others)
- you prefer one vendor handling identity, wallet, and checkout behind a single API
Choose AGIRAILS if:
- the funds should stay on a public chain, in a contract, movable only by published rules
- payment has to release against proven delivery, with the money committed before work starts
- a payment dispute needs a defined, bonded path that ends in an on-chain ruling
- your agent's identity and record should be the agent's own, carried on a public registry
- you want the fee schedule fixed in code and visible before you integrate
Where this connects
What the vault does while the work is in flight: What is agent escrow?
Why funds on a platform ledger and funds in a contract are different categories: What is non-custodial settlement?
Who answers for what when there is no platform in the middle: Who is accountable in a non-custodial agent payment system?
The other comparisons in this series: AGIRAILS vs Nevermined, AGIRAILS vs Google AP2, and AGIRAILS vs Coinbase x402, with the whole series mapped at AGIRAILS comparisons.
The contracts this comparison keeps pointing at: agirails.io
The claim about proven delivery is itself provable: the first agent-to-agent escrow settlement on a public chain is at this BaseScan transaction (February 21, 2026, $3.69 USDC, quote to settlement with no human touching it).
Sources and verification
Last verified: July 2, 2026.
Primary Skyfire sources used for this comparison:
- Skyfire developer documentation: wallets "managed by Skyfire," funding rails, token creation and charging, KYA verification, the Verified Service Guarantee.
- Skyfire Services Agreement: Credits (§3.1), fees and the 30-day notice (§3.4), the dispute guarantee (§3.6), termination (§4).
- KYAPay protocol: the open spec, CC BY-SA license, and the IETF Internet-Draft.
- Skyfire beta exit announcement (March 2025): the enterprise payment network launch.
- Experian Agent Trust announcement (April 2026): KYA as the framework's identity layer, with Cloudflare edge enforcement.
- F5 partnership (March 2026) and Fastly partnership (June 2026).
Skyfire has built the most serious identity layer in agent payments, and gatekeepers need one. A transaction needs an answer about the money. Skyfire keeps that answer on its own ledger, under its own terms; the ACTP answer is a contract address on Base that anyone can read.