1. Paste this into your agent
It tells the agent where our documentation is and how to check its work. Nothing here is secret.
2. Give it your token when it asks
The machine token lives in your console, on the business page, under Connect an AI agent. With the token the agent looks up the rest itself. No account yet? Sign up here, confirm your email from the link we send, and you land straight on that screen.
Create an account| What | Secret? | What the agent does with it |
|---|---|---|
publishableKey |
No, it sits in your page source | Puts the widget on the page; read with the token |
businessId |
No | Names the business it is working on; read with the token |
| Machine token | Yes | Saves and publishes the config. Nothing else needs it |
Treat the token like a password: it should not end up in the repository the agent is building, and Issue a new one in the console replaces it at any time — the widget already on your page keeps working.
3. Check what it did
Open your console: the config the agent published is the one you see, and the requests visitors leave arrive there. Nothing the agent writes reaches your visitors until it passes the same validation your own edits pass.
Embedding it yourself
The same two lines the agent puts on your page, with the publishable key from your console:
Without an account
An agent can read every contract and check a config it assembled without
any keys at all — /api/public/config-schema and
/api/public/configs/validate are open. The account matters only at the
moment of publishing, because that is the moment something appears on your site.