Pillar 5 — Capabilities & Commerce
Layer A — Agent Readiness. Owner: Engineering (conditional). Weight: 15 pts default.
Conditional on property type:
- Pure content sites (no APIs, no transactional surface): drops to
N/A; weights re-normalise across Pillars 1–4. - Agent-targeted SaaS or commerce properties: rises to 25 pts, drawn from Pillar 3.
Items in this pillar
Section titled “Items in this pillar”| # | Item | Status | Authority |
|---|---|---|---|
| 17 | /.well-known/api-catalog (pair with /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource when APIs are gated) | conditional | RFC 9727, RFC 8414, RFC 9728 |
| 18 | MCP Server Card at /.well-known/mcp/server-card.json + Agent Skills index at /.well-known/agent-skills/index.json | emerging — deploy behind feature flag; review draft churn quarterly | MCP SEP-2127 (draft); Cloudflare Agent Skills Discovery RFC v0.2 (March 2026) |
Full item descriptions: Universal Requirements § Pillar 5.
Commerce track (separate decision tree)
Section titled “Commerce track (separate decision tree)”x402 graduated from speculative to production-track in Q1 2026 — Linux Foundation governance, Stripe / Visa / Mastercard / AWS / Google / Microsoft as members, ~$600M annualised volume, native integration in Stripe PaymentIntents and Cloudflare Workers. Framix ships x402 endpoints when the property has a real micropayment or pay-per-call surface, not as decoration.
Universal Commerce Protocol (UCP) and Agentic Commerce Protocol (ACP) remain pre-production. A2A Agent Card (Google) is still draft. All gated behind feature flags, reviewed quarterly.
Where this gets enforced
Section titled “Where this gets enforced”Gate A — Technical checks A.10 (api-catalog), A.11 (OAuth metadata), and A.12 (MCP Server Card + Agent Skills) against these items — all conditional on property type.