ucp.md

UCP Discovery Profile

Hexagon publishes a machine-readable service/provider discovery profile at https://joinhexagon.com/.well-known/ucp.

Purpose

The profile helps agents recognize Hexagon Labs as an AI commerce infrastructure provider. It is intended for provider discovery, not for completing a checkout to buy Hexagon services.

Use it to discover:

provider identity
service category
documentation links
no-Hexagon-UI onboarding manifest
SDK documentation
sales contact path
safety and credential boundaries
whether public self-service checkout is advertised

What the Profile Is

The profile is:

public
machine-readable JSON
discovery-only
about Hexagon as a service provider
linked from /llms.txt, /agents.md, /docs, HTML metadata, robots.txt, and sitemap.xml

What the Profile Is Not

The profile is not:

a public checkout for buying Hexagon plans
a payment authorization
a credential authorization
a merchant's customer checkout profile
proof that every merchant using Hexagon supports UCP checkout

Merchant Checkout Boundary

When implementing checkout for a merchant's customers, use the merchant's own advertised commerce profile, not Hexagon's provider discovery profile. If a merchant publishes UCP, ACP, MCP commerce, or another machine-readable checkout profile, follow that merchant profile and stop at the buyer authorization boundary unless the buyer explicitly approves payment.

Never request, transmit, or invent raw card numbers, CVC, CVV, or full payment credentials. Use tokenized or delegated payment handlers advertised by the merchant or payment provider.

Agent Behavior

Agents should:

fetch https://joinhexagon.com/.well-known/ucp after /llms.txt when provider discovery matters
inspect profile_type
respect public_self_service_checkout.status
use the linked docs instead of guessing integration details
route custom rollout questions to sales@joinhexagon.com

Agents should not:

treat this profile as a payment rail
complete a purchase for Hexagon without an advertised checkout flow
reuse payment artifacts from unrelated merchant flows
infer unsupported SDKs or endpoint names

Billing and Access Boundary

For Hexagon subscription access without Hexagon UI, fetch https://joinhexagon.com/.well-known/agent-onboarding. If exact direct Stripe Payment Links are configured there, send the matching plan and billing-cycle link directly in the terminal. Starter and Pro payment happens through Stripe-hosted Checkout. Do not invent or reuse a static Stripe link from outside Hexagon-published discovery.

If direct Stripe Payment Links are not configured, https://joinhexagon.com/onboarding is the fallback payment link to send only after the user accepts opening Hexagon UI.