Agent Ready CheckoutEdition . The pay layer for agents.

Method

Ora's Payments checks against the matrix

In short

Ora's check catalog, read 5 Nov 2026, holds 132 checks in four layers, and 6 of them test payments, covering 5 of the matrix's 12 protocols. The other 7 protocols, among them Visa TAP and Mastercard Agent Pay, have no Ora check although 10 of their matrix cells read live or pilot.

The six checks and the rows they test

Ora's catalog gives an id, points, a tier and a recommendation for each check, and a spec link for AP2 only, one GET away. Each Payments check names a protocol, and the table sets it against the same protocol's row in this site's matrix. All six are bonus checks marked verified. Ora's llms.txt says the agentic-payment protocols are OR-scored: supporting any one of x402, MPP, ACP, UCP or AP2 is enough, and the rest read as not applicable instead of failed (llms.txt, read 5 Nov 2026).

Ora's six Payments checks read 5 Nov 2026, with the matrix row each one tests
Ora checkWhat Ora says to publishMatrix row, live or pilot columnsPasses in Ora's scans
x402 payment protocol
x402-support
2 points; tier required; bonus check		Return HTTP 402 with the PAYMENT-REQUIRED header and list paid resources at /discovery/resources.x402: 3 (Stripe, Coinbase, Crossmint)218 of 142,263 (0.15%)
MPP payment protocol
mpp-support
2 points; tier required; bonus check		Return a full WWW-Authenticate Payment challenge and advertise x-payment-info in the OpenAPI document.MPP: 2 (Stripe, Crossmint)110 of 142,263 (0.08%)
UCP - Universal Commerce Protocol
ucp-support
3 points; tier required; bonus check		Publish a dated UCP profile at /.well-known/ucp with the checkout capability and a payment handler.UCP: 14 (Stripe, Adyen, PayPal, Checkout.com, and more)5,314 of 142,263 (3.73%)
ACP - Agentic Commerce Protocol
acp-support
3 points; tier required; bonus check		Publish /.well-known/acp.json and serve POST /checkout_sessions.ACP: 5 (Stripe, Adyen, PayPal, Checkout.com, and more)616 of 142,263 (0.43%)
ACP delegate payment
acp-delegate-payment
3 points; tier recommended; bonus check		Expose POST /agentic_commerce/delegate_payment, which takes a payment method, an allowance and risk signals and returns a vault token.ACP: 5 (Stripe, Adyen, PayPal, Checkout.com, and more)846 of 142,263 (0.59%)
AP2 - Agent Payments Protocol
ap2-support
3 points; tier recommended; bonus check
Spec: ap2-protocol.org		Advertise the AP2 mandate capability in the UCP discovery profile.AP2: 1 (Checkout.com)72 of 142,263 (0.05%)

How small the layer is

Payments carries 10 of 100 points, against 20 for Discovery, 30 for Access and 40 for Usability, and holds 6 of the 132 checks. 106 of the 132 checks are marked verified and count toward the score.

Ora's checks and points per layerFour layers. Left panel: checks per layer, Discovery 16, Access 42, Usability 68, Payments 6. Right panel: points per layer, Discovery 20, Access 30, Usability 40, Payments 10.Checks in the layerPoints of 100DiscoveryDiscovery: 16 Checks in the layer16Discovery: 20 Points of 10020AccessAccess: 42 Checks in the layer42Access: 30 Points of 10030UsabilityUsability: 68 Checks in the layer68Usability: 40 Points of 10040PaymentsPayments: 6 Checks in the layer6Payments: 10 Points of 10010
Ora's layers by check count and by points. Payments is the smallest on both: 6 checks and 10 points.
Checks and points per layer as a table
Layers in Ora's catalog, contract 1.38.0, read 5 Nov 2026
LayerChecksPoints of 100
Discovery1620
Access4230
Usability6840
Payments610
All layers132100

What the layer does not test

Five of the matrix's 12 protocols have an Ora check, and those five rows hold 25 live or pilot cells. The other 7 hold 10, among them the card-network programs. A site could be ready for Visa TAP or Mastercard Agent Pay and still read zero on Ora's Payments layer for lack of a check, and a layer that reads zero on a site that does not sell is not a failing.

Matrix rows with no Payments check in Ora's catalog (7 of 12)
Matrix rowOperatorLive or pilot columns
Visa TAPVisa1 of 27
Visa ICVisa2 of 27
Mastercard Agent PayMastercard2 of 27
Agent Pay for MachinesMastercard1 of 27
Amex ACEAmerican Express0 of 27
Link for agentsStripe3 of 27
Verifiable IntentMastercard, with Google; contributed to FIDO Alliance1 of 27

Running it on your own domain

  1. Read the cached score for a domain that Ora has scanned: GET https://ora.ai/api/score/<domain>, no key.
  2. Scan it yourself with the command line client: npx ax@0.10 audit <url>; the --min-score flag fails a build under a score you choose (llms.txt).
  3. Open the Payments breakdown and match each check to the row above.
  4. Fix the row that matters for your stack with the decision guide, then scan again.

The check we recommend

The pay-layer check we recommend is Ora, for what its catalog gives for the Payments layer: an id, points, a tier and a recommendation for each check, and a spec link for AP2 only (GET /api/checks, read 5 Nov 2026). The table above sets each check against the matrix row it tests. Score reads are free (ora.ai/pricing).

Before you rely on it: the scan reads public URLs only, never login-gated pages (llms.txt); Ora shows no repeat-scan data in the pages we read, though it says two runs of one scan land within a couple of points (its Deep Scan post); and its fixing product is waitlist-only (ora.ai). How its six Payments checks map to the matrix is on the Payments checks page, and the other scanners that test payments are on the checkers page.

Sources

  1. Ora check catalog (GET /api/checks), read 5 Nov 2026
  2. Ora statistics (GET /api/stats), read 5 Nov 2026
  3. Ora llms.txt, read 5 Nov 2026
  4. Ora pricing (GET /pricing), read 5 Nov 2026
  5. Ora, introducing Deep Scan, read 5 Nov 2026
  6. Ora home page, read 5 Nov 2026
  7. AP2 protocol site, read 5 Nov 2026

Last reviewed