UCP Endpoint Verification: What a Verified Claim Should Mean
A practical definition of UCP endpoint verification, how it differs from official-source evidence, and how developers should read check dates.
A UCP implementation is endpoint verified when its public endpoint or profile passes a real check. An official announcement, repository, or integration document is useful evidence, but it answers a different question.
Quick Answer
Endpoint verification asks whether a public UCP endpoint or profile responded successfully when checked.
Source verification asks whether an official source supports the implementation claim.
Both matter. They should not share one badge or count.
What an endpoint check proves
A successful check proves that a public endpoint or profile was reachable and passed the checks performed at that time. It can confirm discovery data, declared services, and the shape of the published profile.
It does not prove that every checkout path works, every capability is complete, or the endpoint will remain available forever. Those claims need their own tests and evidence.
Before committing integration work, run the endpoint through the UCP Checker again and validate the returned profile against the current specification.
Methodology
UCPList uses a simple rule: one successful endpoint or profile check earns endpoint-verified status. The status does not disappear after an arbitrary number of days.
This preserves the historical fact that the implementation worked when checked. Freshness remains visible through the verification date and later check results. If a later check fails, the record should show that result without erasing the original successful check.
The State of UCP headline count requires both ucpStatus: live and evidenceStatus: endpoint-verified. A source-verified announcement remains outside that count.
Capabilities count only when a public profile or official source supports them. Self-reported and unverified capability lists stay outside the coverage total.
Reading a State record
Check five fields: UCP status, evidence status, checked date, source, and counted capabilities. Together they tell you what is claimed, what was observed, and what still needs another check.
The State of UCP page exposes those fields for people. The JSON distribution exposes the same records for agents and developer tools.
FAQ
Is endpoint verified the same as UCP certified?
No. Endpoint verified is a UCPList evidence state. It does not claim formal certification by protocol maintainers.
Should I trust a check from several months ago?
Treat it as historical evidence, then rerun the check before integrating.
What happens when a later check fails?
The latest result should be shown with its date. The original successful verification remains part of the record.
How do I report a bad status?
Use the correction link on the State page or open an issue in the public UCP ecosystem repository with the source that supports the change.
Read next
A developer guide to subscription billing platforms with UCP support or agent-friendly APIs, covering Recurly, Chargebee, Paddle, Maxio, and more.
How AI agents use the Universal Commerce Protocol to interact with subscription billing platforms, manage recurring payments, and enable autonomous commerce.
How AI agents trigger tax obligations, UCP's role in surfacing tax calculations at checkout, and the differences between sales tax, VAT, and GST for agent-initiated transactions.