Honeyb Platform API. Search data and the AI answer, one key.

    The SEO API that returns
    the AI answer too.

    Search data and AI-answer data behind one key. Run any prompts for any brand across ChatGPT, Gemini, Perplexity, Claude and four more engines, and get back who was recommended, in what order, with what sentiment, and which pages were cited. Pay per answer. No plan.

    Read the docs
    Engines covered
    ChatGPTAI ModeAI OverviewsGeminiClaudePerplexityGrokDeepSeek

    Why this API exists

    Every rank tracker sells you a dashboard. This one sells you the answers. The same pipeline that measures Honeyb customers every day, open to your prompts, by the answer.

    8

    engines behind one request, six of them searching the live web

    $0.08

    per answer on any engine; held at submission, settled to what arrived

    ~1 min

    from POST to enriched results and citations

    One request

    Prompts in, enriched answers out.

    Submit a task: a brand, a list of prompts, the engines to ask. Honeyb runs every prompt on every engine, reads each answer, and hands back the structure you would otherwise build a team to extract.

    • Who was named. Your brand and every competitor in the answer, with the offset of the first mention, so "listed first" is a number.
    • In what tone. Sentiment toward your brand with a confidence score, per answer, per engine.
    • From which pages. Every citation with its domain, page type and position, and whether the cited page mentions you.
    GET /api/platform/v1/tasks/{id}/results
     
    {
    "prompt": "What is the best billing platform for SaaS?",
    "engine": "chatgpt",
    "brandMentions": 1,
    "totalMentions": 4,
    "competitorsMentioned": ["Chargebee", "Stripe Billing", "Zuora"],
    "sentiment": "positive",
    "sentimentConfidence": 0.86,
    "answer": "For most SaaS companies the strongest options are ...",
    "createdAt": "2026-09-06T11:13:31Z"
    }

    Endpoints

    Five endpoints. One question: what does AI say about this brand?

    Submit, poll, read. Base URL app.honeyb.ai/api/platform/v1, bearer key, JSON both ways. The reference documents every field.

    POST/tasks

    Your prompts, one brand, the engines you choose. Every prompt runs once on every engine and comes back enriched: mentions, order, sentiment, citations.

    GET/tasks/{id}

    Live progress: answers expected, completed and failed, and the exact charge once every engine has answered.

    GET/tasks/{id}/results

    One row per prompt per engine: the full answer text, who was named, how often, in what tone.

    GET/tasks/{id}/citations

    Every page the engines read to answer: domain, page type, position in the source list, and whether it mentions the brand.

    GET/tasks

    Everything you have run, newest first, with counts and charges, for reconciliation and reporting.

    Pricing

    Pay for answers, not seats.

    $0.08 per answer, the same on every engine. A task's price is prompts times engines, held from your credits when you submit and settled to the answers that actually arrived. Credits are prepaid, never expire, and there is no subscription and no seat. Two prompts on three engines: 48 cents.

    POST /api/platform/v1/tasks
    {
    "brand": { "name": "Acme Billing", "url": "acmebilling.com" },
    "engines": ["chatgpt", "gemini", "perplexity"],
    "prompts": [
    "What is the best billing platform for SaaS?",
    "Alternatives to Zuora for mid-market companies"
    ]
    }
    => "priceCents": 48, "status": "running"

    Build with it

    Wherever you are building, the answers go in.

    Inside your product

    Building a marketing platform, a CMS, an agency portal? Add AI visibility as a native feature: one POST per brand, and the enriched answers are yours to render.

    Inside your agents

    Your automations can submit a task, wait for it, and act on the result: draft the comparison page the engines keep citing competitors from, then re-run the prompts next week.

    Inside your reports

    One task per client, the same prompts every week. Mention rate, first-mention position and sentiment become the columns of a report that took no analyst hours.

    Inside your research

    Run a category's buying questions across every engine and read the citations. The domains that keep coming back are the ones a category is won on.

    Why it holds up

    Built on the pipeline Honeyb runs for its own customers every day.

    Real engines, live web

    Six of the eight engines (ChatGPT, Gemini, Perplexity, Claude, Google AI Mode and AI Overviews) search the web before they answer and cite what they read, so the results reflect today, not a training snapshot. Grok and DeepSeek answer from memory, a useful baseline.

    Enriched, not raw

    Every answer comes back with brand and competitor mentions, first-mention offsets, sentiment with confidence, and every citation classified by page type. The text is there too.

    Pay for answers

    $0.08 per answer on every engine, from prepaid credits. The price is held when you submit and settled to the answers that actually arrived. No seats, no plan, no minimum term.

    Compared with a classic SEO data API

    Search data and the AI answer, in one call.

    Classic SEO data APIs stop at the ranked page. Buyers now start one step later, at the answer an engine gives them, and that is where this API begins.

    What one call returns

    ClassicA ranked results page, a keyword row or a backlink list.

    HoneybThe AI answer itself, enriched: who was recommended, in what order, with what sentiment, and which pages the engine cited.

    Coverage

    ClassicGoogle and Bing result pages.

    HoneybEight AI engines today, from ChatGPT and Google AI Mode to Grok and DeepSeek. Google and Bing rank tracking in early access on the same key.

    Sources

    ClassicThe URLs on the results page.

    HoneybEvery citation behind the answer, classified by page type, so you know which pages shape the recommendation.

    What to do next

    ClassicLeft to you.

    HoneybThe gap is in the response: which competitors were named ahead of you, in what tone, and the exact pages the engine read to decide.

    Shape

    ClassicTask queues, generic endpoints, decoding on your side.

    HoneybOne endpoint per job, JSON an agent can read as-is, submit then poll then read.

    Pricing

    ClassicPer request or per row, across tier tables.

    HoneybPer answer, one price on every engine, prepaid credits that never expire.

    Where it fits

    ClassicThe cheapest bulk pull of search-page data.

    HoneybThe call an agent makes when it needs search data and the AI answer together.

    API lines

    One key, one balance, every line.

    The AI answer lines are live today. The classic SEO data lines are in early access on the same key, each with its own page, endpoints and per-request pricing.

    FAQ

    Frequently asked questions.

    Start with the docs.

    Every endpoint, request and response shape, with examples. Ten minutes from your key to first results.

    Open the docs

    Free to start

    Get recommended by AI search models.

    Run a free AI search visibility check, then let the Honeyb agent do the work that gets you into the answers.

    ChatGPTClaudeGeminiPerplexity