Automated tool for ab testing ideas & examples for your site
Sign In Get Started
Agent Gateway 5 min read

abTestBot Agent Gateway

Connect AI agents and LLM assistants to abTestBot's A/B testing research and experiment management services. Supports both MCP (Model Context Protocol) and A2A (Agent-to-Agent Protocol).

What You Can Do

  • Register a new website and get back the tracking snippet to install
  • List your registered websites
  • Get AI-analyzed site intelligence (industry, competitors, keywords)
  • List and filter A/B test ideas
  • Generate new AI-powered test ideas
  • Generate variant code from a natural-language prompt — no pre-existing idea required (e.g. "change the hero price from $99 to $499 and update the Stripe link")
  • List, inspect, and create experiments

All calls are billed per-credit. Purchase credits →

Prerequisites

  1. An abTestBot account on any plan
  2. Credits — buy a pack from Settings → Billing → Agent Credits (Starter $9/100, Growth $39/500, Scale $129/2,000). Enterprise plans include unlimited usage — no credits needed.
  3. An API key (sk_live_...) from Settings → API (available once your first pack is purchased, or automatically on the Enterprise plan)

MCP Setup (Claude Desktop, Cursor, Zed, etc.)

Add to your MCP client config:

{
  "mcpServers": {
    "abtestbot": {
      "url": "https://agent.abtestbot.com/mcp",
      "headers": {
        "Authorization": "Bearer sk_live_YOUR_KEY_HERE"
      }
    }
  }
}

Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "abtestbot": {
      "url": "https://agent.abtestbot.com/mcp",
      "headers": { "Authorization": "Bearer sk_live_..." }
    }
  }
}

Then ask Claude: "List my sites on abTestBot" or "Generate 5 A/B test ideas for site [id]"

A2A Setup (n8n, LangGraph, AutoGPT, CrewAI, etc.)

Agent Card URL (for discovery):

https://agent.abtestbot.com/.well-known/agent.json

Task endpoint:

POST https://agent.abtestbot.com/a2a/tasks
Authorization: Bearer sk_live_...
Content-Type: application/json

{
  "id": "your-task-id",
  "message": {
    "role": "user",
    "parts": [
      {
        "type": "data",
        "data": {
          "tool": "list_sites",
          "params": {}
        }
      }
    ]
  }
}

Health Check

curl https://agent.abtestbot.com/health
# → {"ok":true}

Security

Your sk_live_ key is a bearer token — anyone with it can spend your credits (or, on Enterprise, use your unlimited agent-gateway access) until you revoke it. Treat it like a password.

Safe placements

  • Server-side environment variables, CI/CD secret stores
  • Local MCP client config files (e.g. claude_desktop_config.json) — these stay on your machine and aren't shipped anywhere
  • A password manager

Never

  • Frontend JavaScript or browser-exposed code
  • Git repositories, even private ones (git history is forever)
  • Public blog posts, tweets, Stack Overflow, YouTube screenshots — use the placeholder sk_live_YOUR_KEY_HERE in examples
  • Plain-text chat / email

If a key leaks: Settings → API → revoke it, then generate a new one. Revocation propagates within 60 seconds (our auth-cache TTL). Deactivated keys cannot be reactivated — you'll need to generate a replacement.

Building a public tool on top of abTestBot? Route all calls through your own backend so the key never reaches end users' browsers. If you ship a desktop/CLI tool, have each end user generate their own key in their own abTestBot workspace — don't bundle a single key into distributed binaries.

Server-side, we only store the SHA-256 hash of each key — so even if our database leaked, the raw keys can't be recovered. But if the raw key leaks from your code or repo, it is fully usable by anyone who finds it until revoked.

Reference