Integrations
Three ways to install it
The gateway is the same code in all three: your facts, rendered as markdown, at your own URLs. What changes is who runs it — you, or us.
None of these are installable yet — here is exactly where each one is.
All three are built and tested in the open. What each is waiting on is a marketplace, a directory or a registry, and those are listed on the cards rather than hidden behind a waitlist form. In the meantime the scanner works on any URL today, with no account, and tells you what agents currently get from your site.
Scan a URL→Shopify
Managed app
Install from the App Store. Nothing to configure.
You click Install and approve the permissions. We read your catalog, keep it synced, and answer agents at your own storefront URLs through Shopify’s App Proxy — no theme edit, no DNS change, no code. An agent asking your product page for markdown gets your live price, availability, policies and pages.
- Products, collections, policies, pages and blog posts
- Prices and stock read from Shopify, never recalculated
- Draft and archived products are never served
- Uninstall removes everything; we keep no copy
Paid — we run and monitor the endpoint
Not yetAwaiting Shopify App Store listing and review.
How App Proxy serving works→WordPress
Plugin, GPL-2.0-or-later
Activate the plugin. That is the entire setup.
Your posts, pages and WooCommerce products start answering agents that ask for markdown, at the URLs you already have. It runs entirely on your own server and makes no outbound request of any kind — no ping, no usage beacon, no version check. Your content is never sent anywhere, including to us.
- Posts, pages and WooCommerce products
- Generates /llms.txt from your own content
- Sends Vary: Accept, so caches keep humans and agents apart
- Search engines always get your normal HTML
Free forever — it never touches our servers
Not yetAwaiting WordPress.org plugin directory submission and review.
What the plugin serves→Any stack
npm package
One middleware, wired to your own source of truth.
For everything that is not Shopify or WordPress: Next.js, Express, Fastify, Cloudflare Workers, or a Shopify App Proxy you host yourself. You point it at the data you already have — a database, an API, a CMS — and it renders the five content shapes agents ask for. It returns a response, or it returns null and your normal pipeline runs untouched.
- Adapters for Next.js, Express, Fastify and Cloudflare Workers
- Products, catalogs, policies, documents and collections
- A source that throws is treated as no-match, never a 500
- UCP, ACP and MCP endpoints, version-pinned
How the pricing works
Free if you run it. Paid if we run it.
The SDK and the WordPress plugin run on your own server and cost us nothing per request, so they are free and always will be — no metering, no page limit, no seat count. The Shopify app is the one you pay for, because we run the endpoint, hold the credentials and keep your catalog synced. You are buying the operations, never the capability.
No capability is locked
Every Shopify store can also self-host the App Proxy adapter from the free SDK and pay us nothing. The app exists because most merchants would rather not run an endpoint, not because the capability is locked.
Full pricing →Not on this list
Wix, Squarespace, Rails, Django, or something you wrote yourself
Anything that lets you put code in front of your own routes can serve agents today — that is what the SDK is. Anything that does not is a harder problem, and we would rather say so than sell you a side-door endpoint on a URL your customers never see.
The test we apply before committing to a platform is whether an app can serve markdown at the page’s canonicalURL on the merchant’s own domain. Shopify passes because of its App Proxy; WordPress passes because you control the whole request. Most hosted site builders expose no equivalent, and an agent-readable copy of your site living somewhere else is a worse product than none — it splits your content across two addresses and invites exactly the mismatch we refuse to ship.