Open Knowledge Format (OKF) vs Agent Readability Spec (ARS)
They sit at the same step and overlap in purpose; the fields above are the basis for choosing.
| Open Knowledge Format OKF | Agent Readability Spec ARS | |
|---|---|---|
| Lifecycle step | 4 Read: Give me the content | 4 Read: Give me the content |
| Answers | How can an organization package durable, structured knowledge (schemas, metrics, playbooks, runbooks) so both humans and agents can read, produce, and trust it without a bespoke SDK? | How readable is this site's content for AI agents, and what specifically should be fixed? |
| Governed by | Google Cloud open-source project; canonical repository is GoogleCloudPlatform/open-knowledge-format on GitHub (moved out of the GoogleCloudPlatform/knowledge-catalog monorepo in August 2026, which now carries only a frozen, unmaintained snapshot) | Vercel; published in Vercel's own Knowledge Base with no external standards process |
| Status (issuer's words) | "An open specification; contributions, alternative implementations, and adoption beyond Google products are all explicitly welcomed" | A specification and scoring checklist, not a protocol; framed as best practices to implement voluntarily |
| Version | v0.2 (2026-08) | current (last updated 2026-03-23 per a secondary source; no version number or publication date is given on the page itself) (2026-03) |
| Form / transport | document format | document format |
| Found at | /okf/index.md | none |
| Implementation | shipping — Google Cloud (Knowledge Catalog and 4 sample bundles: GA4, Stack Overflow, Bitcoin, Acme Retail), OpenKnowledge (OKF linter plugin), and agenticweb.wiki (163-concept OKF v0.2 knowledge bundle at /okf/index.md) | shipping |
| Evidence | 4 verified | 2 reported, 1 verified |
| Primary use case | Serve readable content to agents | Serve readable content to agents |
| Last verified | 2026-10-23 (current) | 2026-10-23 (current) |
| Specification | https://github.com/GoogleCloudPlatform/open-knowledge-format/blob/main/SPEC.md | https://vercel.com/kb/guide/agent-readability-spec |
When to use which
- Choose Open Knowledge Format when your question is “How can an organization package durable, structured knowledge (schemas, metrics, playbooks, runbooks) so both humans and agents can read, produce, and trust it without a bespoke SDK?” and you accept its maturity: status ""An open specification; contributions, alternative implementations, and adoption beyond Google products are all explicitly welcomed"", implementation shipping (Google Cloud (Knowledge Catalog and 4 sample bundles: GA4, Stack Overflow, Bitcoin, Acme Retail), OpenKnowledge (OKF linter plugin), and agenticweb.wiki (163-concept OKF v0.2 knowledge bundle at /okf/index.md)).
- Choose Agent Readability Spec when your question is “How readable is this site's content for AI agents, and what specifically should be fixed?” and you accept its maturity: status "A specification and scoring checklist, not a protocol; framed as best practices to implement voluntarily", implementation shipping.
Read the full articles
- Open Knowledge Format: How can an organization package durable, structured knowledge (schemas, metrics, playbooks, runbooks) so both humans and agents can read, produce, and trust it without a bespoke SDK?
- Agent Readability Spec: How readable is this site's content for AI agents, and what specifically should be fixed?