okf · open knowledge format

Expertise, installable.

Knowledge bundles for AI agents — published by the organizations that own the expertise, discoverable in one place, verifiable at install.

installokfhub/guide
resolve via github.com/okfhub/registry
org membership — checked
content sha — pinned
concepts land in .claude/knowledge/
$npx okfhub add okfhub/guide
livehttps://okfhub.io/api/mcp

Files land in .claude/knowledge/ — or skip files and read live over MCP. details →

The web’s next reader isn’t human.

Every era rewrote knowledge for its reader — pages for eyes, apps for thumbs, concepts for agents. OKF is the format of that layer; okfhub is its registry — where agents discover, verify and install expertise.

old webnew web
pagesconcepts
docsbundles
browsersagents
scrapingreading
viewingciting

Expertise, packaged for agents.

A knowledge bundle is a portable collection of linked concepts — plain Markdown with structured metadata. Humans can read it. Agents can consume it. Git can version it.

google/stack-overflow — a live listing: 49 concepts · 51 cross-links

stack-overflow/49 files
references/ · 32
badge_classes.md
close_as_off_topic_reason_types.md
30 more
tables/ · 16
badges.md
comments.md
14 more
datasets/ · 1
stackoverflow.md

Skills are verbs. Bundles are nouns.

Skills change what an agent does, for one harness. Bundles change what it knows. They’re complementary — skills give capabilities; bundles give those capabilities domain context.

skill

how to deploy

how to call

how to test

changes what it does

bundle

what the product does

why the API behaves this way

which policy applies

changes what it knows

Install expertise. Keep it current.

Your API changes. Your policies change. A useful bundle isn’t a document you publish once — it’s maintained expertise that evolves with the domain. Installs pin an exact SHA, okfhub update shows drift before changing a thing, and updates never delete your edits.

Non-destructive by design — install & update details →

lifecyclemaintained, not archived
sha pinned at install — never floats
update --dry-run lists drift, changes nothing
the knowledge stays fresh, not snapshotted

Don’t trust the registry. Verify the source.

okfhub doesn’t decide whether knowledge is trustworthy. It gives agents evidence they can evaluate — dated, re-checkable, never a verdict.

  • 01 origin — GitHub org membership checked
  • 02 domain — DNS TXT challenge proven
  • 03 content — SHA-256 pinned at install

see the full evidence on a live listing →

evidencegoogle/stack-overflow
·listingio.github.google/stack-overflow
·contentsha d44368c · pinned
·checks6 passed · checked Aug 31, 2026
·context8985 stars · 765 forks · popularity ≠ safety

Your knowledge has a new audience.

Your agents

Give internal agents a canonical source of organizational knowledge.

Your customers’ agents

Let agents acting on behalf of your customers understand your products, policies and APIs directly.

Your developers

Portable, versioned knowledge instead of another proprietary documentation system.

Your business

Understand how agents discover and use your expertise — agent analytics, later.

Publish once — your expertise reaches agents wherever they work. Publish yours →

What’s next

now

  • public bundles
  • GitHub + DNS verification
  • OKF validation
  • CLI + live MCP

next

  • private bundles
  • paid access via Polar
  • prompt-injection checks
  • freshness monitoring

later

  • agent analytics
  • publisher attribution
  • commercial knowledge

Later is a thesis about where the agent web is going — not a promise.

The web was built for people.
Knowledge can now speak to agents.