Specs

Four specs, each with a version and a changelog; JSON Schemas and test vectors anyone can test against, for each wire format and for how the vocabulary reads a door’s names. The specs and the code are MIT. The census’s counts are open data under CC BY 4.0, credited “Surfing Dog census, surfingdog.ai, CC BY 4.0”.

Spec	Version	Last changed
What an AI agent can do at a business	version 2	15 October 2026
Agent inbox manifest	surfingdog-inbox/0	15 October 2026
Receipts	claims version 2	27 September 2026
The census of what AI agents can do	method version 1	18 October 2026

Check yours

Paste a manifest, a receipt or an acknowledgement to see whether it holds to these specs, and if not, why. The check runs in your browser and sends nothing anywhere.

For machines

/spec/index.json lists every spec, its version and its files.
/spec/capabilities.json is the latest capability vocabulary. Each version stays at its own address: /spec/capabilities/v1.json, /spec/capabilities/v2.json.
/spec/schemas/<name>.json is every JSON Schema, such as manifest.json. A schema’s $id is its address.
/spec/vectors/<name>.json is every set of test vectors, such as receipts-v2.json and capability-names.json, how a tool’s, skill’s or operation’s name is read as capabilities. An implementation is right when it agrees with them.
/spec/vocab/<name>.json is every other vocabulary: door types, categories, door report classes, the agentic score’s rules.
Every JSON file under /spec/ can be read from any origin.

The same files, with Zod schemas and the conformance check as code (checkManifest, checkReceipt, checkAcknowledgement), are in packages/spec.

How they change

New fields and values are added. Nothing is renamed, and every version stays published.
A reader ignores a field it does not know.
A change that would break a reader comes with a new version: surfingdog-inbox/1, receipt claims ver: 3, vocabulary version 3.
Each spec says what changed, and when, in its changelog.