OKF-Web v1.1

Can an AI answer your shoppers' questions?

A hosted service that keeps the answer yes: your store's knowledge verified, measured, and readable by the assistants shoppers already use, on a flat monthly plan. A full independent audit is there when you want the deep look, never as a requirement. Everything we do is open to inspection, and your bundle is yours to keep.

See the hosted serviceSee a full sample report

Measured, not promised

17.4×
less context per answered question vs raw pages
How much less text an AI has to read to answer from the bundle than from the same store's raw pages: cheaper, faster, and less room to guess wrong.
0.949
coverage on the reference store (raw HTML: 0.615)
The share of test questions the knowledge could actually answer, graded by a judge; 1.0 would be all of them.
39
shopper questions across 13 archetypes
The questions real buyers ask, about shipping, warranty, fit, returns, and availability, across every knowledge kind.
2,407
tokens per question served to the model
The average reading cost per answered question. Smaller means faster, cheaper answers.

Measured by the open evaluator on the reference bundle, the complete example store that ships with the toolchain, and re-read from its recorded scorecard at every build. No number here is typed by hand; run okf-web evaluate on your own bundle for yours.

The hosted service

Start where the ongoing value is. Hosted monitoring keeps your store's knowledge bundle verified and current: scheduled re-evaluation against the questions shoppers actually ask, drift detection that flags source changes for a human to approve instead of silently rewriting, and managed translation, all on a flat monthly plan with an included allowance, quoted at onboarding.

There is no meter running against you. The platform-connector serving tier stays free until AI engines demonstrably consume your bundle, under the published, versioned activation policy. Leaving is one command; your complete bundle goes with you, and the open tools serve it unchanged.

Why we built this

The toolchain behind this service is open source and complete; nothing here is a feature withheld to be sold. We offer the hosted edition for stores that would rather have careful hands run it, and the hosted work funds the commons it stands on, not the other way around.

Three commitments follow from that, and they are structural rather than sentimental:

fetch, for people and machines alike, always.

and the open tools serve it unchanged. Free egress is a tested acceptance criterion, not a promise.

state what would let you do the same thing free, and the billing rules are published, versioned, and never applied retroactively.

The audit, when you want the deep look

The audit is optional and never a gate: monitoring does not require it. It is the extended benefit for a store that wants its answerability measured to the bottom, once, with an independent judge on the record:

feed ingestion that refuses live values, drafts placed under a single write gate, provenance recorded from the first byte.

state exactly how much human attention each fact received; a machine never wears a human label.

knowledge to the bundle, and an independent judge model grades the answers; the builder never grades its own work.

a hash-verified record of exactly what was delivered.

One-off, invoiced on delivery, with no subscription hiding inside it. The number on the button is the number on the invoice.

Where this stands, honestly

OKF is a real, published knowledge format; the ecommerce convention we build on is this project's own. No generative engine fetches OKF bundles yet. What you are buying works without that bet: the service measures answerability today, and the schema.org markup and llms.txt we derive from your verified knowledge land against today's engines. If engines adopt bundle-style knowledge, yours is already published; if they don't, the verified tier still feeds your markup and your own assistants.

You could do this yourself, free

The toolchain is open source (Apache-2.0), and the report is not a gated feature:

pip install okf-web
okf-web init <your-bundle>
okf-web evaluate <your-bundle> --write-scorecard
okf-web report <your-bundle>

What the hosted service sells is the labor and the standing behind it: curation by careful hands, an independent judge model, and signed third-party delivery. Access to the tool is never part of the price.

What it costs

Hosted monitoring is a flat monthly plan with an included allowance, quoted at onboarding. It covers scheduled re-evaluation, drift detection, and managed translation, and its serving tier bills only after verified AI-engine consumption of your bundle, per the published, versioned activation policy.

The audit is an optional one-off, invoiced on delivery. No subscription, no meter, no recurring charge.

For AI assistants

This site is itself an OKF bundle at /.well-known/okf/, with llms.txt and JSON-LD derived from human-attested concepts. To query it live from an MCP-capable assistant:

okf-web mcp --url https://<this-domain>/.well-known/okf/