For AI agents

Put a working widget on a site you are building. Everything in one fetch: /llms-full.txt.

Public endpoints are on https://mindthefront.com, owner endpoints on https://console.mindthefront.com.

1–3. Build and validate without an account

curl https://mindthefront.com/api/public/config-schema -o schema.json

curl -X POST https://mindthefront.com/api/public/configs/validate \
  -H "Content-Type: application/json" --data @config.json

{ "valid": false, "errors": [
  { "path": "/flow/steps/confirm", "rule": "flow-lint",
    "message": "Field \"phone\" is required but is not filled on every path to the submit step \"confirm\"" }
] }

path is a JSON Pointer to the node that breaks the rule: /flow/steps/confirm, /submission/properties/appointment. Status is 200 in both outcomes; valid is the verdict. Nothing is stored. Every rule and its message: writing a config. Declaration-to-input mapping: widget catalogue.

4–5. Publish with the owner's token

The owner copies the token from the console — their business page, "Connect an AI agent". An owner without an account signs up at https://console.mindthefront.com/#agent, confirms their email from the link we send, and lands on that screen. Don't create the account yourself: the account appears only once the owner confirms the email. The token is a secret: keep it out of the repository, out of committed files and out of anything you print back.

BUSINESS=$(curl -s https://console.mindthefront.com/api/businesses/current -H "X-Owner-Token: $TOKEN")
ID=$(echo "$BUSINESS" | jq -r .id)
KEY=$(echo "$BUSINESS" | jq -r .publishableKey)

CONFIG=$(curl -sX POST https://console.mindthefront.com/api/businesses/$ID/configs \
  -H "X-Owner-Token: $TOKEN" -H 'Content-Type: application/json' \
  --data @config.json | jq -r .id)

curl -X POST https://console.mindthefront.com/api/configs/$CONFIG/publish -H "X-Owner-Token: $TOKEN"

"Issue a new one" in the console replaces the token: the previous one gets 401 at once, the embedded widget keeps running on the same publishable key.

6. Embed

Put the snippet on the page with $KEY as publishableKey.

Constraints to design around