Sato Hub
Payment Rail

Agent Payments Protocol (AP2)

Open protocol from Google for secure agent-led payments across traditional and crypto rails, with a crypto-native x402 extension built with Coinbase, Ethereu...

  • Sato Score72
  • ChainsEthereum, Base +1
ActiveVerifiedQuiet · 4mo ago

Agent Payments Protocol (AP2) is an open-source payment rail by Google on Ethereum and Base, with last code activity on 2026-06-17 (Quiet). Latest release on 2026-04-28. Sato Score 72/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-23. How the score works →

See how to install Agent Payments Protocol (AP2) →

Last commit Jun 17, 2026 · Last release Apr 28, 2026 (v0.2.0) · ★ 3,233

Listed from ap2-protocol.org on 2026-06-08. Install: not attempted. Evidence →

Website ↗Docs ↗GitHub ↗

Next step

Watch Agent Payments Protocol (AP2)

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on google-agentic-commerce/ap2 before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

AP2 (Agent Payments Protocol) is an open protocol announced by Google for initiating and settling agent-led payments, using cryptographically signed Verifiable Credential 'Mandates' to create verifiable, user-authorized transaction trails. It is an extension to the Agent2Agent (A2A) protocol and supports both traditional rails and crypto/stablecoins. The crypto-native path is the A2A x402 extension, developed by Google in collaboration with Coinbase, the Ethereum Foundation, and MetaMask.

Sato Score

72/100· High

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
20/35
Code transparency
20/20
Interface verifiability
0/10
Docs & demo
10/10
Listing transparency & provenance
14/15
Independent verification
8/10

Independently verified — listing reviewed against evidence, never self-reported.

View verification & embed badge →History →How the Sato Score works

Evidence — listed vs checked · what the words mean

Listed from ap2-protocol.org on 2026-06-08. Install: not attempted.

ClaimValueEvidenceSourceChecked
Chains supportedEthereum, Base, Multichainself-reportedap2-protocol.orgas of 2026-10-23
Verification statusVerifiedreview date and evidence link not recorded on this listing✓ reviewed—not dated
Recent activitylast release 2026-04-28 · last commit 2026-06-17observedgithub.com/google-agentic-commerce/AP22026-10-23
Install worksdocumented by the project, not run by Sato Hubnot attempted: no falsifiable install+entry probe from deploy_specself-reportedgithub.com/google-agentic-commerce/AP2as of 2026-09-14
Website answersanswered (HTTP 200)observedap2-protocol.org2026-10-23
Daily check record90 of 90 daily checks since 2026-07-25 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-22
Built byGoogleconfidence 0.80self-reportedgithub.com/google-agentic-commerce/AP2as of 2026-06-25
Creator profilehttps://github.com/google-agentic-commerceconfidence 0.80self-reportedgithub.com/google-agentic-commerce/AP2as of 2026-06-25
Deploys aspip, Self-hostedconfidence 0.70self-reportedgithub.com/google-agentic-commerce/AP2as of 2026-06-25
Works withA2A, MCP, ADK, x402, Universal Commerce Protocolconfidence 0.85self-reportedap2-protocol.orgas of 2026-06-25
Tagsagent-payments, google, coinbase, metamask, x402, stablecoins, a2a, standard, m…confidence 0.80self-reportedap2-protocol.orgas of 2026-06-25
Demo availableyesconfidence 0.70self-reportedgithub.com/google-agentic-commerce/AP2as of 2026-06-25
Sato Score72/100 (High)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-23

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — not run by us — no falsifiable install+entry probe from deploy_spec

Runtime: Python 3.11+ (git install — no registry package yet)

uv pip install git+https://github.com/google-agentic-commerce/AP2.git@main
from ap2.sdk.mandate import MandateClient
from ap2.sdk.generated.payment_mandate import PaymentMandate
# run demos: bash code/samples/python/scenarios/a2a/human-present/cards/run.sh

You supply: GOOGLE_API_KEY (or Vertex AI) to run the agent samples, no wallet — card/A2A payment mandates

Read from the project’s own docs as of 2026-09-14. What a deploy spec is →

Observed record — 90 daily checks since 2026-07-26

100%of 90 checks since 2026-07-26 succeeded
Currently responding for 90 days
Succeeded
90
Failed
0
Their error
0
Unattributed
0

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 37 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-23, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
72
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Ethereum, Base, Multichain
Agent types
Payment Protocol, Commerce Agent
Open source
Yes
Pricing
Free (open protocol)
Deploys as
pip, Self-hosted
Works with
A2A, MCP, ADK, x402, Universal Commerce Protocol
Last checked
2026-10-23

Marketplace Signals

  • ▸ Demo available

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#agent-payments#google#coinbase#metamask#x402#stablecoins#a2a#standard#mcp#adk#verifiable-credentials

Where Agent Payments Protocol (AP2) fits

TradingPayments

Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets, What Are Onchain Agents?

See something inaccurate or outdated?Submit a correction →

Recent Activity

All news →

Releases and posts from Agent Payments Protocol (AP2), pulled from its GitHub and X.

Releasegoogle-agentic-commerce/AP2Apr 28, 2026

AP2 v0.2.0

This is the second release of AP2. It focuses on providing Human Not Present flows.

EthereumBaseMultichain
GitHub ↗
Releasegoogle-agentic-commerce/AP2Sep 16, 2025

AP2 v0.1.0

0.1.0 (2025-09-16) Features Create Agent Payments Protocol (AP2) ( e66fc0b )

EthereumBaseMultichain
GitHub ↗

Listing History

Recorded changes to Agent Payments Protocol (AP2)'s listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Jul 26, 2026
    Sato Hub began tracking this listing
  2. Jun 25, 2026
    Enriched: deployment options, has demo, marketplace notes
  3. Jun 25, 2026
    Auto-enriched: tags, supported integrations, creator name, creator profile url
  4. Jun 16, 2026
    Edited: deploy spec

Compared with

Alternatives to Agent Payments Protocol (AP2) →x402 vs AP2 →

Appears in

Related Resources

Coinbase AgentKit

Active
Framework

Coinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.

BaseEthereumMultichain
Active★ 1.3k

Hyperliquid

Active
VenueVerified

Onchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.

MultichainHyperliquid
Recent★ 508▸ Jun 2023

Model Context Protocol (MCP)

Active
Standard

Anthropic's open standard for connecting AI systems to external tools and data sources.

Unknown
Active★ 9.5k

Reference

QuestionsShowHide

Questions people ask about Agent Payments Protocol (AP2)

Is Agent Payments Protocol (AP2) open source?
Yes. Agent Payments Protocol (AP2) is open source under the Apache-2.0 license; the repository is https://github.com/google-agentic-commerce/AP2. Checked as of 2026-10-23.
Which chains does Agent Payments Protocol (AP2) support?
Agent Payments Protocol (AP2) lists support for Ethereum, Base, Multichain as of 2026-10-23.
Is Agent Payments Protocol (AP2) still maintained?
The most recent code activity Sato Hub observed was on 2026-06-17 (last commit 2026-06-17, last release 2026-04-28), which Sato Hub labels "Quiet". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run Agent Payments Protocol (AP2)?
Python 3.11+ (git install — no registry package yet). Install: uv pip install git+https://github.com/google-agentic-commerce/AP2.git@main. Entry: from ap2.sdk.mandate import MandateClient from ap2.sdk.generated.payment_mandate import PaymentMandate # run demos: bash code/samples/python/scenarios/a2a/human-present/cards/run.sh. This is taken from the project's own documentation and has not been reproduced by Sato Hub.
Is Agent Payments Protocol (AP2) verified on Sato Hub?
Sato Hub holds one earned check for Agent Payments Protocol (AP2): Independently verified — listing reviewed against evidence, never self-reported. Its Sato Score is 72 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Agent Payments Protocol (AP2) — Sato Hub." Sato Hub, updated 2026-10-23, accessed 2026-10-24. https://satohub.ai/resources/agent-payments-protocol-ap2

Data last refreshed 2026-10-23; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.