LLMentions
Docs · Quickstart

Quickstart

Sign in, get your API key, and get your first AI visibility result with confidence intervals in about two minutes, over MCP, the CLI or REST.

↓ Markdown for agents

LLMentions measures how AI answer engines (ChatGPT, Google AI Mode, Gemini, Claude, Perplexity, Grok and others) mention and cite your brand, and audits whether those engines can read your site. It has three interfaces with the same capabilities and the same names: an MCP server for agents, the llmentions CLI, and a REST API.

This page takes you from nothing to a real result.

1. Sign in and get your key

Go to api.llmentions.com/login and sign in with Google, GitHub or email. You get:

  • a workspace with $1 of free usage, no card needed
  • your API key (sk_live_…), shown once. Copy it into your secrets manager or shell:
terminal
export LLMENTIONS_API_KEY=sk_live_…

Using the CLI? Skip the copy and paste. llmentions login opens the same sign-in page in your browser, confirms a one-time code, and saves the key to ~/.config/llmentions with mode 0600:

terminal
llmentions login

Test keys are free. Create one with llmentions keys create dev --test (or POST /v1/keys with "test": true). sk_test_… keys run against mock engines with realistic variance, return the same shapes and errors, and are never charged. Build against a test key, then swap in the live one.

2. Ask your first question

Pick the interface you'll use most. All three call the same service and return the same data.

MCP (Claude Code shown; other clients in MCP)

terminal
claude mcp add --transport http llmentions https://api.llmentions.com/mcp \
  --header "Authorization: Bearer $LLMENTIONS_API_KEY"

Then ask your agent:

Using llmentions, check how ChatGPT, Perplexity and Claude answer "best crm for startups", 5 samples each, and whether Acme is mentioned. Quote it first.

The agent calls account_get, then ai_answers with dry_run: true for the price, then runs it.

CLI

terminal
llmentions ask "best crm for startups" --brand Acme --domain acme.com \
  --competitor Rival --engines chatgpt,perplexity,claude -n 5

REST

terminal
curl -s https://api.llmentions.com/v1/ai/answers \
  -H "authorization: Bearer $LLMENTIONS_API_KEY" \
  -H 'content-type: application/json' \
  -d '{
    "prompts": ["best crm for startups"],
    "engines": ["chatgpt", "perplexity", "claude"],
    "samples": 5,
    "brand": "Acme",
    "domain": "acme.com",
    "competitors": ["Rival"]
  }'

Add "dry_run": true (or --dry-run) to get the exact price without running anything. Five samples on three engines is 15 answers: about $1.00 on these API engines, or $0.05 on queued consumer-app engines.

3. Read the result

You get every answer in one normalized shape, plus a report because you passed brand:

json
{
  "data": {
    "answers": [
      {
        "engine": "perplexity", "source": "api", "prompt": "best crm for startups",
        "mentions": [ { "brand": "Acme", "is_target": true, "position": 1 },
                      { "brand": "Rival", "is_target": false, "position": 2 } ],
        "citations": [ { "domain": "acme.com", "class": "owned" },
                       { "domain": "reddit.com", "class": "ugc" } ],
        "search_queries": ["best crm for startups 2026"]
      }
    ],
    "report": {
      "summary": "Acme was mentioned in 7/15 answers: 47% (95% CI 25–70%).",
      "samples": 15,
      "overall": [
        { "brand": "Acme", "is_target": true, "mentioned": 7, "samples": 15,
          "rate": 0.47, "ci_low": 0.25, "ci_high": 0.70, "share_of_voice": 0.41 }
      ],
      "engines": [ "…per engine…" ],
      "sources": [ { "domain": "reddit.com", "class": "ugc", "answers": 6, "rate": 0.4 } ]
    }
  },
  "meta": { "charged_usd": 1.0, "balance_usd": 0.0 }
}

The fields that matter:

  • rate with ci_low and ci_high. Acme was named in 7 of 15 answers: 47%, with a 95% interval of 25–70%. The interval is wide because 15 answers is a small sample. See Methodology.
  • citations[].class tells you whether the engine cited you (owned), a competitor, a forum (ugc), a reference site, or other press (earned).
  • source says where an answer came from: the official api with native search, the consumer app (ui), or a parametric probe with search off. They are never pooled silently.

One answer is one sample. AI answers vary from run to run, so never act on a single answer. Use 5 or more samples per prompt and engine, and treat a change as real only when it is significance-tested.

4. Track your brand over time

For ongoing measurement, create a project with the prompts your buyers ask, then run panels against it. Runs are stored and compared run-over-run with a two-proportion test.

terminal
llmentions projects create Acme --domain acme.com --competitor Rival \
  --prompt "best crm for startups" --prompt "hubspot alternatives for small teams"
llmentions run Acme -n 5 --queued --dry-run   # quote: queued consumer-app answers are $0.003
llmentions run Acme -n 5 --queued             # starts the panel, waits, prints the report
llmentions report Acme                        # latest run vs the previous one
llmentions answers Acme --missing             # the answers that left you out, and what they cited

Don't know which prompts to track? llmentions suggest --category "crm for startups" --brand Acme --track researches the buyer questions in your category and adds them.

5. Check that AI can read your site

Being cited starts with being readable. AI crawlers don't run JavaScript, and many CDNs block them by default.

terminal
llmentions audit acme.com

The audit crawls your site as AI bots see it, checks robots.txt for every AI bot, and lists issues most-severe first, each with a fix. See Site audit.

Where next