Rubric / Actionability

Commerce protocol manifest

actionability.commerce_protocols

weight 1deterministicemerging

The site declares an agentic-commerce discovery manifest (x402, UCP, or ACP), so a buying agent can learn how to transact from the domain alone.

Adoption of what this check tests is still climbing, so failing it is an opportunity rather than a defect. Remediation lists rank these after established fixes, and the weight moves only when measurement earns it.

Definition

Check ID

actionability.commerce_protocols

Category

Actionability

Weight

Counts toward the score

Yes.

Evaluated by

A fixed rule with no threshold of our choosing. The same input always produces the same verdict.

Standard maturity

emerging

Canonical spec

None. This check has no published external specification — it is an AgentSpeed rule.

Introduced in

r2026.11.0

Retired in

Still active.

History

Every change to the instrument— including the versions that changed this check

Machine-readable

/rubric.json— this check, and every other, as data

How often this check is right

No rate published. Too few labelled cases to publish a rate: 1 flagged case (30 needed to publish), 1 defective case (30 needed to publish). The counts are the honest answer here. The matrix behind actionability.commerce_protocols is 2 labelled cases — reported here rather than turned into a percentage that would read as more certain than the evidence is.

Corpus v1, measured under rubric r2026.11.0. Full method and every other check at /rubric/accuracy.

How to fix it

If you sell to agents, publish the discovery manifest for the commerce protocol you support: `/.well-known/x402.json` (x402), `/.well-known/ucp` (UCP), or `/.well-known/acp.json` (ACP). Any one of the three passes — agents pre-flight these before attempting a transaction.

Does your site pass this check?

Free scan, 30 seconds, no signup — this check and the other 35, with the exact evidence for each verdict.

Scan my site →