Agent Onboarding

Onboard a site with et. Current instructions are on Install et, Sign in, and et commands. MCP setup is on Claude Code, Codex, and ChatGPT.

Install et with the API script in step 1.

Ordered checklist

1. Install the CLI: curl -fsSL https://api.endlesstesting.ai/install.sh | sh. How to install et.
2. Sign in: et login --email [email protected], then et login --code 123456. The code arrives by email. Details are on Sign in. Settings are at https://dash.endlesstesting.ai/. Never fabricate a code.
3. Add the site: et site add https://<domain>.
4. Install the snippet: et snippet <site> --text prints the HTML. <site> is the host, such as example.com. Paste that HTML into the site’s <head> via its shared layout/template (Next.js app/layout.tsx, Astro BaseLayout, Nuxt app.vue, etc.).
5. Verify: after redeploy, curl -s https://<domain>/ | grep -E "AB_CONFIG|api/sdk\.js". If nothing matches, the install failed.
6. Start a round: et round start <site>. Add --url https://<domain>/ to test one page.
7. Monitor: et status <site> shows what is live. et results <site> shows winners and lift after a round finishes.
8. Kill switch: et kill <site> on stops serving variants. et kill <site> off lets them serve again.

MCP integration

The CLI doubles as an MCP server. Add it to your agent once and use native tools instead of shelling out.

Claude Code

claude mcp add endlesstesting -- et mcp

Cursor

.cursor/mcp.json:

{
  "mcpServers": {
    "endlesstesting": {
      "command": "et",
      "args": ["mcp"]
    }
  }
}

Rules for agents

• Do not fabricate test results. Winners need real traffic. Wait for data before reporting lift.
• Do not install on auth pages, admin panels, or iframes. Only on public pages that drive conversion.
• Do not skip et site add. Register the site before et snippet. Run et brand autofill <site> so the copy generator has brand context.
• Do not commit the account token. The CLI writes it to ~/.config/endlesstesting/token.
• Prefer CLI → MCP → REST. The REST API is the last resort for custom integrations.

Troubleshooting

Symptom	Cause	Fix
et: command not found	CLI not on PATH	The install script saves ~/.local/bin/et. Add that directory to PATH
{"error":"not signed in"}	No account token stored	Run et login --email, then et login --code
{"error":"site not found"}	That host is not on this account	Run et site add, then pass the host to later commands
SDK snippet not in deployed HTML	Paste didn’t land in prod layout	Check SSG/SSR output, not local source
Variants never allocate	weight: 0 on all variants	This was a v0 bug: upgrade backend to latest