UCP
Universal Commerce Protocol: open, signed, schema-first.
KarmanFlow documents UCP discovery at /.well-known/ucp, uses standard dev.ucp catalog aliases, and maps canonical cart, checkout, order, payment, fulfillment, catalog, and extension UI models while keeping state changes command-backed.
What it does
Three things this surface gives you.
- Catalog search and lookup expose UCP aliases while native KarmanFlow tools keep richer operator freshness envelopes.
- Cart and checkout are model-supported now; callable checkout waits for one command-backed policy and receipt boundary.
- RFC 9421 signatures are verified when tenant or partner policy requires them, and whenever signature headers are present.
- UCP spec dates and KarmanFlow profile dates are separate, so future UCP versions can land as new adapters.
Discover the configured capability set
Worked example.
# Discovery profile is documented at /.well-known/ucp.
# Preview cells publish capability ids, protocol bindings,
# canonical model maps, and JSON Schema URLs when enabled.
curl -s "$KARMANFLOW_API_URL/.well-known/ucp" | jq '
{
capabilities: (.ucp.capabilities | keys),
models: (.canonical_models.models | keys)
}
'
# Sample output (Phase-1 surface):
# {
# "capabilities": [
# "dev.ucp.shopping.catalog.search",
# "dev.ucp.shopping.catalog.lookup",
# "dev.ucp.shopping.checkout",
# "com.karmanflow.protocol.model_registry"
# ],
# "models": ["cart", "checkout.session", "order", "payment.intent"]
# }Preview
Run a working integration path.
Request a guided preview workspace, or bring a sample integration shape to a working session and we will walk through it on a call.