What does 'agent-ready' mean for a website?

The site publishes machine-readable descriptions of itself alongside its human-readable pages, so AI answer engines and agents can navigate, understand, and cite it without scraping and guessing: schema.org JSON-LD entities on every page, a curated llms.txt content map, a robots.txt that explicitly allows the major AI crawlers, a sitemap, and an Open Knowledge Format bundle at /knowledge/.

What is the Open Knowledge Format (OKF)?

OKF is an open, Apache-2.0-licensed specification introduced by Google Cloud in June 2026: knowledge represented as a directory of markdown files with YAML frontmatter, where the file path is a concept's identity and normal markdown links form the knowledge graph. Only one frontmatter field (type) is required, and no SDK or runtime is needed to read a bundle. AI OS generates an OKF bundle for every hosted site and can export the platform's own knowledge as one.

Is the FAQPage structured data guaranteed to match what visitors see?

Yes, by construction: the FAQPage JSON-LD is generated from the exact same question-and-answer pairs the page visibly renders in its FAQ section. There is no separate hand-maintained markup that could drift out of sync with the content.

Is AI OS content provenance the same as C2PA Content Credentials?

No, and the docs say so plainly. AI OS provenance uses C2PA vocabulary for interoperability, but it is not certified C2PA. It is an Ed25519-signed sidecar binding a hash of the served homepage, plus an unsigned JSON-LD disclosure on each page. The signed sidecar is the integrity artifact; the on-page disclosure is transparency, not tamper-evidence.

Why disclose that a site was AI-generated at all?

Machine-readable AI-generation disclosure aligns with emerging transparency rules such as EU AI Act Article 50, and honest provenance builds trust with both visitors and answer engines. The disclosure states how the site was made; the cryptographic signature lets anyone verify the served content hasn't been altered since it was signed.

Agent-Ready Sites

The web's fastest-growing readers are not people — they are AI answer engines and agents. Every site AI OS generates ships a complete machine-readable layer alongside its pages: schema.org JSON-LD, a curated llms.txt, an AI-crawler-allowing robots.txt, a sitemap, an Open Knowledge Format (OKF) bundle, and Ed25519-signed content provenance. All of it is emitted deterministically from the site's own content — no extra AI calls, and nothing that can drift out of sync with what visitors see.

Structured data (JSON-LD)

Site-wide — Organization and WebSite entities on every page
Per page — a WebPage entity with canonical URL and description
FAQPage — built from the exact question/answer pairs the page's FAQ section visibly renders, so the markup can never disagree with the content
Actions — a ContactAction only when the page genuinely has a contact capability; the emitter is deliberately conservative and never claims capabilities a static site cannot verify

llms.txt, robots.txt & sitemap

Each site serves a curated /llms.txt content map (title, description, page list, and a pointer to the knowledge bundle) so answer engines can navigate deliberately instead of crawling blind. The generated robots.txt explicitly allows the major AI crawlers — an engine that cannot read a site cannot cite it — and a standard sitemap.xml lists every page, including dynamically generated ones.

The Open Knowledge Format bundle

OKF is a vendor-neutral open specification from Google Cloud (June 2026, Apache 2.0) for agent-ready knowledge — it provides a shared format any producer can write and any agent can read: a directory of markdown files with YAML frontmatter, where file paths are concept identities and ordinary markdown links form the knowledge graph. No SDK, no runtime — any agent that can read files can consume a bundle.

Every hosted site publishes one at /knowledge/:

index.md — the site as a Website concept, linking to every page concept
pages/*.md — one concept per page carrying its actual content (FAQ pairs, pricing tiers, stats) in typed, readable markdown
provenance.md — how the site was generated and how to verify it

AI OS offers the same in reverse: the platform can export its own knowledge — the agent registry and documentation map — as a validated OKF bundle for any OKF-aware tool to ingest.

Content provenance

Generated sites carry a two-layer provenance record:

The signed sidecar — /.well-known/aios-provenance.json, an Ed25519-signed credential binding a SHA-256 hash of the served homepage. It is re-generated and re-signed on every rebuild, so the binding never goes stale, and anyone can verify it against the platform's published public key
The on-page disclosure — schema.org CreativeWork JSON-LD stating the site was AI-generated (aligned with EU AI Act Article 50 transparency expectations), plus training/data-mining preference assertions. This layer is unsigned by design: it is disclosure, not tamper-evidence

Honest naming:

AI OS provenance uses C2PA vocabulary for interoperability but is not certified C2PA — the sidecar is the integrity artifact, and the docs never claim otherwise.

API Endpoints

GET /api/provenance/public-key

The platform's Ed25519 public key for verifying site provenance sidecars.

POST /api/provenance/verify

Verify a provenance credential against served content.

GET /api/okf/export.zip

Operator-only: the platform's own knowledge (agent registry + docs map) as a validated OKF bundle.

Frequently asked questions

Does any of this cost tokens to generate?

No. The entire machine-readable layer is emitted deterministically from the site's plan — the same content the pages render — with zero additional AI calls.

Can the structured data drift from the visible content?

Not by construction — FAQPage markup, OKF concepts, and llms.txt are all generated from the same source the pages render from, on every build.

Is this certified C2PA?

No — C2PA vocabulary for interoperability, honest about not being certified. The Ed25519-signed sidecar is the verifiable integrity artifact.

← Security Web Studio Business Tools →