[tonyspiro]

Disclosure first: I wrote CAP. I've kept this page to what the spec, the repository and the directory show today, and marked it Draft. Please push back on anything that reads like a pitch.

What changed

Adds a page for CAP, the Concierge Agent Protocol (/standards/cap), in Act after NLWeb, with status Draft. A company publishes /agent.txt; a visiting agent posts a question to {CAP}/messages and gets back one message from the company's own agent, with an optional OAuth device sign-in for account questions. NLWeb is the standard people will confuse it with, so the PR also adds an "NLWeb vs CAP" pair to /compare, a line on /which, a related link on NLWeb's page, and changes the "twelve" counts to thirteen. README and spec-pins.json are regenerated with npm run readme and npm run pins.

• Why draft: the spec is 1.0 Draft (first published October 16, 2026). The protocol's directory lists six sites that pass its check, but all six are served by Cosmic, my company: five are Cosmic's own sites and one is a customer's. That doesn't meet "beyond the authors' own demos." No AI assistant is publicly known to look for agent.txt on its own.
• Neighbours, stated neutrally: NLWeb answers from the site's structured data; CAP hands the question to whatever agent the company already runs, and adds account questions. The spec maps a CAP message onto an A2A task.
• Benchmark: the page cites the authors' own benchmark and says nobody else has published a test.

If CAP lands after PACT (#15), the counts become fourteen; happy to rebase.

Sources

• Specification (1.0 Draft): https://conciergeprotocol.org/spec (spec.md)
• Changelog: https://github.com/conciergeprotocol/cap/blob/main/CHANGELOG.md
• Governance (draft status, when 1.0 becomes final): https://github.com/conciergeprotocol/cap/blob/main/GOVERNANCE.md
• Directory of sites that pass the check: https://conciergeprotocol.org/directory (and https://conciergeprotocol.org/api/doors)
• Benchmark: https://conciergeprotocol.org/benchmark
• node scripts/spec-drift.mjs check spec-pins.json --only cap reports ok for the pin.

Checklist

• Every new or changed claim links a primary source.
• If I changed a status, the evidence meets the rules in content/contribute.md.
• I only changed last_verified on pages where I rechecked every claim.
• Plain words, no em dashes.

[vercel]

@tonyspiro is attempting to deploy a commit to the Ora Team on Vercel.

A member of the Team first needs to authorize it.