Points of Focus

• Fetch.ai linked Google’s AP2 mandates with uAgents and Skyfire Pay.
• The bridge maps payment approval, processing, completion, and cancellation across both systems.
• The release adds working code, but no live merchant or transaction-volume data.

Fetch.ai has turned its Skyfire payment work into a runnable checkout flow for AI agents. The new A2A Cart Store example lets an agent build a cart, request payment through Fetch.ai’s protocol, and complete the transaction through Skyfire Pay.

In an Aug. 2 post, Fetch.ai said agent commerce needs a common way to move from product discovery to payment. Its public code connects an A2A and AP2-based store to a uAgent through the SingleA2AAdapter, then translates payment messages between the two systems.

Agentic commerce cannot stop at product discovery.

Agents also need an interoperable way to complete the transaction.

The A2A Cart Store example connects:

A2A/AP2 store → uAgents adapter → https://t.co/kJ9URVpOul Payment Protocol → @trySkyfire Pay

Under the hood:… pic.twitter.com/gNbCSGqqCL

— Fetch.ai (@Fetch_ai) August 2, 2026

Fetch.ai connects AP2 checkout with Skyfire Pay

At checkout, the store creates an AP2 CartMandate containing the order total and payment method. Fetch.ai’s adapter then converts it into a RequestPayment message.

After the buyer approves the payment, Skyfire provides a payment token. The adapter turns that approval into an AP2 PaymentMandate, allowing the store to verify and process the charge. A successful payment completes the order, while a failed payment cancels it.

Google launched AP2 in September 2025 to create a shared authorization record for purchases made by AI agents. The protocol uses signed mandates to record user approval, cart details, and payment instructions across cards, bank transfers, and crypto. Fetch.ai’s bridge translates those AP2 records into the message format used by uAgents.

New code extends Fetch.ai’s earlier Skyfire relationship

Skyfire had already named Fetch.ai among its launch partners on June 26, 2025, when it introduced identity and payment services for autonomous agents. The latest release adds a reproducible store flow rather than announcing a first-time partnership. Fetch.ai also provides a separate example in which a seller agent charges USDC through Skyfire before delivering an AI-generated image.

The example still stops short of commercial deployment. Fetch.ai describes the cart store as a minimal runnable example that requires Python, local servers, and Skyfire seller credentials. It provides no merchant count or transaction-volume data. Fetch.ai’s payment specification remains version 0.1.0, while Google described AP2 as v0.1 in March 2026.