Can an AI answer your shoppers' questions?

Measured, not promised

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, on a flat monthly plan. The price is on the button, the included allowance beside it, and nothing else recurs.

Buying starts the work: your store's pages become a draft knowledge bundle, a person reads it before anything is measured, and monitoring begins from there. There is no meter running against you. Leaving is one command; your complete bundle goes with you, and the open tools serve it unchanged.

Connect your store platform

If your store runs on Shopify, WooCommerce or BigCommerce, the connector builds the bundle from your catalog itself. You approve a read-only connection in your store's own admin, and from then on your products and policy pages flow into drafts on a daily sync, with every change waiting for a person to approve before it is published. Nothing is ever written back to your store, and uninstalling the app from your store ends the connection.

The connector tier is free until AI engines demonstrably consume your bundle, under the published, versioned activation policy, and you hear from us before any first charge. After that it is the same flat monthly plan as hosted monitoring, nothing more.

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:

• Readers never pay. The knowledge published for you is free to

fetch, for people and machines alike, always.

• You can always leave. One command exports your complete bundle,

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

• Every price survives daylight. Wherever we ask to be paid, we

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:

• Your bundle is built through the same open pipeline anyone can run:

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

• A person verifies the content and signs it by name. Trust tiers

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

• An evaluation puts shopper questions across thirteen kinds of store

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

• When every check passes, the auditor countersigns your published

bundle and the attestation joins the public transparency log, valid until your content goes stale (180 days at most). If a check fails, the report is still delivered; no signature and no log entry are issued.

• You receive the report, the scorecard, and the bundle itself, with

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; the price is on its button above and the allowance beside it. 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. Cancel any month; your complete bundle leaves with you.

The connector for Shopify, WooCommerce or BigCommerce costs nothing until AI engines demonstrably consume your bundle, with notice before the first charge; from then on it is the same flat monthly plan.

The audit is an optional one-off, invoiced on delivery, and it includes the auditor's countersignature when the checks pass. 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/