On this page
Implementation guide
Same objects. Your transport.
The core contract is JSON, independent of how an agent and business exchange it. Validate the same core objects against the published schemas in every binding.
REST and MCP reference bindings
These bindings are reference, not production, and make no UCP conformance claim.
Quote requests are asynchronous: submit a request, then poll for status. The optional status-change webhook is deferred in this reference, and calls are not held open while work completes. OAuth 2.0 bearer authorization is described only; the local reference server does not implement authentication. Rate limits are communicated through per-business response headers, and these bindings set no rate-limit values.
Binding roadmap
No hosted API or checkout adapter is implemented in this repository. Apart from the local REST and MCP reference bindings above, the order below is the roadmap, not a list of available integrations.
| Transport | Priority | Purpose |
|---|---|---|
| REST / HTTP | First | Exchange manifests, requests and quotes using ordinary HTTP services. See the local reference binding above for endpoint paths, methods and error envelopes. |
| MCP | First | Expose quoting operations to agent clients. See the local reference binding above for tool definitions. |
| GraphQL | Next | A future binding for graph-oriented clients; no schema or resolvers are published. |
| A2A | Later | A future agent-to-agent binding; no UQP task mapping is defined. |
Authorization: OAuth 2.0
OAuth 2.0 is the intended authorization foundation for protected operations. UQP has not yet defined scopes, grant profiles, issuer discovery or token requirements. OAuth is an authorization framework, not by itself an identity protocol.
Do not put credentials or contact information in quote answers. Enforce business access and consent at the service boundary; JSON Schema validation is not an authorization check.
Quote here. Checkout elsewhere.
UQP runs up to the binding Quote and is intended to hand an explicitly accepted quote to an existing checkout, including UCP or ACP. Those links describe the other protocols; they are not evidence of a working UQP adapter or an endorsement.
Keep the business’s existing deposit checkout. Confirm artist review and explicit client approval of the payment amount and policies before handoff, and enforce the allowed lifecycle transitions. UQP does not collect payment or define a checkout payload in this draft. A deposit counts as paid only after payment processor confirmation, never client self-report. The provider is merchant of record; UQP never holds funds. See the Estimate, binding Quote and proposed UCP mapping.
What you can implement now
- Validate manifests, requests, models and quotes against draft 2020-12 schemas.
- Evaluate synthetic Tattoo pack inputs with the reference evaluator and explicit timestamp.
- Keep transport-specific errors, authentication and checkout outside the core object contract.