The AIOX Protocol: An Open Standard for AI-Optimised Content

Standards win when they’re open. The history of the web is littered with proprietary “standards” that never escaped one vendor: ActiveX, Flash, AOL Keywords. The ones that lasted — HTML, RSS, Schema.org, OpenAPI — were freely implementable, well-documented, and not under any single company’s control.

The AIOX Protocol is in that second category, deliberately.

What’s in the spec

The published AIOX Protocol v1 defines five things:

1. The Capsule format — JSON-LD shape, required and optional fields, AIOX-namespaced extensions.
2. The discovery mechanism — how AI systems find Capsules on a site (manifest at /aiox.json, well-known endpoint, sitemap integration).
3. The licensing vocabulary — allowed values for the aiox:license field, semantics of each (indexing-only vs indexing-and-citation vs license-required, etc.).
4. The signing scheme — Ed25519 key generation, signature canonicalisation, public-key publication at /aiox-pubkey/.
5. The versioning rules — semver, backwards-compatibility guarantees, revocation procedures.

The spec is normative — meaning if you implement it correctly, your output will be interoperable with any other AIOX-compatible tool. Non-conformant implementations are still allowed (it’s an open spec), but they don’t get to claim AIOX compatibility.

Why we’re not patenting it

Patenting the protocol would be commercially convenient for AIOX (the company) for about 18 months. Then it would become an adoption blocker, and 5-10 years from now we’d be the next “remember that company that owned ActiveX?” lesson in textbooks.

The same applies to trying to brand “AIOX” as the only legitimate implementation. The dashboard you log into at app.aioxsuite.com is one reference implementation. There can — and we hope, will — be others.

Governance going forward

For v1.x, AIOX (the company) shepherds the spec. As adoption grows, we plan to move the protocol under a neutral governance body — likely the W3C or an independent foundation. The exact mechanism is being worked out with early implementers; if you’re interested in contributing, get in touch.

v1 backwards compatibility is guaranteed for at least 5 years. Major breaking changes will be coordinated via published RFCs with 6-month minimum lead time.

Where to start if you want to implement

• Read the protocol spec.
• Check the open-source examples on GitHub (Capsule generator, validator).
• Use the AIOX dashboard’s Capsule preview tool to see live, valid output from real WordPress sites.
• Join the community Discord — implementer questions get answered there fastest.