Serpmantics

Get the current user's available AI tokens Returns the number of AI tokens available to the authenticated user. These tokens fund EVERY AI feature in SERPmantics — meta, outline, intent, internal-links, EEAT, EEAT competitors, score, AND the AISSistant prompts. The endpoint lives under /aissistant for historical reasons but the balance is shared across all AI features. Do NOT confuse with guide-creation credits (see /api/v1/credits). For a combined view (credits + tokens) prefer /api/v1/credits.

无需输入参数。

Get user balance (guide credits + AI tokens) Returns the authenticated user's full balance. SERPmantics has TWO distinct currencies: - **credits** (`credits`): how many NEW GUIDES the user can still create. Consumed once per guide creation. `"unlimited"` if the user's plan grants unlimited guide creation (`hasUnlimitedCredits: true`). - **AI tokens** (`tokens`): pool consumed by every AI feature (meta, outline, intent, internal-links, EEAT, EEAT competitors…). Each feature has its own cost — call `/api/v1/tokens-usage` to get the per-feature pricing. Do not confuse the two: running out of `credits` blocks new guides; running out of `tokens` blocks AI features inside existing guides.

无需输入参数。

Get E-E-A-T analysis results for a guide's competitors Retrieves the E-E-A-T analysis results for the top competitors of a guide. Poll this endpoint until `pending` is `0` to know when the full analysis is complete. Individual competitor results are available as soon as their `status` is `done`.

Start an E-E-A-T analysis on a guide's top SERP competitors Starts an asynchronous E-E-A-T analysis on the top competitors of the guide's SERP. Each competitor is fetched and scored individually. Use GET /api/v1/eeat-competitors to poll for results until `pending` reaches `0`. **Token cost:** This endpoint charges `eeatCompetitorsTokensCostPerCompetitor` (see /api/v1/tokens-usage) per competitor analyzed, up to 10 competitors. Example: 10 competitors × 5 tokens = 50 tokens. 6 competitors × 5 tokens = 30 tokens. The number of competitors corresponds to the deduplicated URLs in the guide's top-10 SERP results (available via GET /api/v1/guide).

Get E-E-A-T analysis results Retrieves the result of an E-E-A-T analysis. `guideId` is **always required**: access is granted on the guide, so a request without it is answered with `404 Guide not found`. `eeatId` is an optional filter on top of it: pass it to fetch one specific analysis of that guide, omit it to fetch the latest one. An `eeatId` that does not belong to `guideId` is answered with `404`, never with the other account's data. Poll this endpoint until `status` is `done` (results available) or `failed`.

Start an E-E-A-T analysis on a guide content Starts an asynchronous E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) analysis on the HTML content provided for a given guide. The analysis runs in the background — use GET /api/v1/eeat to poll for results until `status` is `done` (or `failed`). **Note:** This endpoint uses tokens (check /api/v1/tokens-usage for the cost, might vary).

Get search intent analysis for a guide Retrieves existing intent analysis results for a guide

Generate search intent analysis for a guide Analyzes search intent for a guide and optionally analyzes provided content against that intent. **Note:** This endpoint uses tokens (check /api/v1/tokens-usage for the cost, might vary).

Delete generated intent analysis for a guide Removes previously generated intent analysis for the given guide.

Get internal linking suggestions for a guide Retrieves existing internal linking suggestions for a guide

Generate internal linking suggestions for a guide Analyzes a guide and generates internal linking suggestions based on content analysis. **Note:** This endpoint uses tokens (check /api/v1/tokens-usage for the cost, might vary).

Delete generated internal-links suggestions for a guide Removes previously generated internal-links suggestions for the given guide.

Get generated meta titles and descriptions for a guide Retrieves generated SEO meta titles and descriptions for a guide

Generate SEO meta titles and descriptions for a guide Generates optimized meta titles and descriptions based on guide content analysis. **Note:** This endpoint uses tokens (check /api/v1/tokens-usage for the cost, might vary).

Delete generated meta for a guide Removes previously generated meta titles/descriptions for the given guide.

Get generated page structure for a guide Retrieves the generated page structure (flat heading list) for a guide.

Generate content outline for a guide Generates a content outline based on SERP analysis for a guide. **Note:** This endpoint uses tokens (check /api/v1/tokens-usage for the cost, might vary).

Delete generated outline for a guide Removes previously generated outline data for the given guide.

Get API token usage costs for different endpoints Returns the number of tokens required for each API endpoint operation. Note: `eeatCompetitorsTokensCostPerCompetitor` is a **per-competitor** cost. The total cost of POST /api/v1/eeat-competitors equals this value × the number of competitors analyzed (deduplicated URLs in the guide's top-10 SERP, capped at 10).

无需输入参数。

Read an AI citation test, poll until it is done Returns the test started by `POST /api/v1/tools/citation-check`. While `status` is `pending` or `running`, call again every 3 seconds: each engine fills in as soon as it has answered. When `status` is `done`, at least one engine answered; `summary.citedBy` engines cite your domain out of `summary.enginesAnswered` engines that answered. When `status` is `failed`, `failureCode` says why (NO_ENGINE_ANSWERED, TIMEOUT, INTERNAL). Per engine: `cited` is true when a source of the answer is on your registrable domain or one of its subdomains, and `citedUrls` lists those pages; `mentioned` is true when your brand name appears in the answer text, which is NOT a citation. `status` no_answer means the engine showed no answer for this question (Google often shows no AI Overview), which is not a failure. No quota is consumed. The `checkId` is random: whoever holds it can read the test, which is what makes share links work. Tests expire after 30 days. Reads that are not attributed to an account are capped at 1000 per IP address and per UTC day, far above any legitimate polling: crossing it returns 429 READ_RATE_LIMITED with `Retry-After`.

Test whether ChatGPT, Perplexity and Google AI Overview cite a website for one question (free tool) Asks one question to three AI answer engines (ChatGPT with web search, Perplexity, Google AI Overview) in the chosen market, and reports for each engine whether your domain is cited as a source (`cited`, a citation on your registrable domain or one of its subdomains), whether your brand is named in the answer (`mentioned`, which is NOT a citation), which of your pages are cited, an excerpt of the answer, its sources, and the domains cited instead of yours. **One answer, on one day.** This is a snapshot, not a lasting measure: AI answers change from one week to the next, and between two calls. Run the test again to compare. **Asynchronous, poll the result.** This call only starts the test and answers HTTP 202 with a `checkId` and a `pollUrl`. Call `GET /api/v1/tools/citation-check?checkId=...` every 3 seconds until `status` is `done` or `failed`; a test usually takes less than 2 minutes. MCP clients must call the `get_citation_check` tool again until the status is terminal. **Identical questions are reused for 24 hours.** The same question (case and spaces ignored) in the same market, asked less than 24 hours ago, returns the engine answers already collected, recomputed for your domain: HTTP 200 with `reused` true and `status` already `done`. Nothing is paid for again, and your daily quota is given back. **Domain.** Send a domain name or any URL of the site: it is reduced to its registrable domain (`https://www.example.co.uk/blog/` becomes `example.co.uk`). IP addresses, local names and unknown suffixes return 400 INVALID_DOMAIN. **Tiers, per UTC day.** - Without an API key, free anonymous tier: 1 test per day per IP address. - Signed-in account, or API key of an account whose plan includes API access: 10 tests per day. The API key of an account whose plan does NOT include API access does not authenticate, and the call returns 401. Remove the `Authorization` hea

Read a comparison of editorial velocities, poll until it is done Returns the comparison started by `POST /api/v1/tools/editorial-velocity/comparisons`. While `status` is `pending` or `running`, call again every 15 seconds. Each site has its own `state` (queued, running, done, failed); its numbers are null until it is done, never zero by default. `analysisId` links to the full analysis of the site (GET /api/v1/tools/editorial-velocity?analysisId=...). `summary.median` and `summary.max` are computed on the competitors measured (`summary.measuredCompetitors`), never on your own site; `summary.own` is the perMonth of your site and `summary.gap` is median minus own. `recommendation.perMonth` is the number of articles per month to publish to keep the median pace of the competitors. It is only given with at least 3 competitors measured; otherwise `recommendation` is null and `recommendationReason` says why (code too_few_competitors, `measured` the number measured). `status` failed happens when the Google results of the keyword could not be read or held no competitor (failureCode SERP_FAILED), or when the comparison could not be started (failureCode INTERNAL); nothing is analysed and everything is given back. `billing` says what the comparison cost and what was given back, place by place (`refunds`, with the reason site_failed, reused, unused_place, serp_failed or not_started, and the status refunded, pending or review). `underReview` is present only when true, the automatic refund stopped and is checked by our team. It names no account. Reading settles the refunds that are due, whoever reads. No quota is consumed. Whoever holds the comparisonId can read it, which is what makes share links work. Comparisons expire after 30 days. Reads not attributed to an account are capped at 1000 per IP address and per UTC day (shared with the reads of analyses), and crossing it returns 429 READ_RATE_LIMITED.

Compare the editorial velocity of competitors, paid in tokens (account only) Measures how many articles each site publishes per month, for a list of sites or for the sites ranking in the Google top 10 of a keyword, then returns the median of the competitors and a recommendation for your own site. Each site is an editorial velocity analysis (same engine as createEditorialVelocity). **Paid, ONLY WITH THE USER'S EXPLICIT AGREEMENT.** 20 tokens per site analysed. With `sites`, the price is 20 tokens times the number of distinct sites, your site included. With `keyword`, the number of sites is only known once Google is read, so the maximum is charged, 5 tokens for the search results plus 20 tokens for each of the 10 places (plus one for `ownSite`), 205 or 225 tokens, and the unused places are given back as soon as the results are read. Before calling, tell the user the price and their token balance, and call only after they agree. Never retry on your own after an error. **What is given back.** The tokens of a site that cannot be measured (blocked, no sitemap, no dates, unreachable, timeout, daily capacity reached), of a site served by an analysis of the same domain less than 7 days old or already running (nothing was read for you), of an unused place, and everything when the search results cannot be read or the comparison cannot start. Refunds happen at the first read that sees them, whoever reads, or within the next hours if nobody reads. `charged` in the answer is what stays charged after the refunds already made by this request. **Asynchronous, poll the result.** This call answers HTTP 202 with a `comparisonId` and a `pollUrl`. Call `GET /api/v1/tools/editorial-velocity/comparisons?comparisonId=...` every 15 seconds until `status` is `done` or `failed`. Sites are analysed a few at a time, a comparison takes from a few minutes to 3 hours. MCP clients must call the `get_editorial_velocity_comparison` tool again until the status is terminal. **Input.** Exactly one o

Read an editorial velocity analysis, poll until it is done Returns the analysis started by `POST /api/v1/tools/editorial-velocity`. While `status` is `pending` or `running`, call again every 5 seconds; `progress` gives the current stage (robots, sitemap, pages, summary) and `pagesRead` out of `pagesTotal`. When `status` is `failed`, `failureCode` says why (BLOCKED, the site refuses to be read; NO_SITEMAP; NO_DATES, pages read but none shows a readable publication date, neither structured data, nor a date tag, nor a "Published on" mention; UNREACHABLE; TIMEOUT; INTERNAL) and `publications` is null. A failed analysis is never a zero. When `status` is `done`, `publications.total` articles were published in `window` (12 full months, UTC), `perMonth` is total / 12 and `perWeek` total / 52.14. `ci95` is only meaningful when the analysis was sampled (`method.sampled`). A `total` of 0 with `ci95` present comes from a sample: it does not prove that the website published nothing, and neither does a 0 with `method.undecidedSections` not empty (sections whose reading stopped before a verdict, counted nowhere). Otherwise, a 0 covers what was read in full: the whole site, or only its dated sections when `method.undatedSections` is not empty. A 0 with `publications.otherDatedPages` above 0 means that dated pages were read, but nothing shows that they are articles (product pages, event calendars): it adds to the meaning of the 0 above, it never replaces it. `method.inferredSections` names the sections without article markup counted from the dates read in their pages (`itemprop` attribute or `<time>` element). `method.sameDaySections` names the sections where at least 80% of the pages counted share the same day: those pages are counted, the list is only a hint to check the website (grouped publication, or dates changed in bulk). `method.discovery` says what the news pages linked from the home page and the RSS or Atom feeds added to the sitemap; its `articlesCounted` is the part of

Measure how many articles a website publishes per month and per week (free tool) Reads the sitemap of one website and the date shown on each of its pages, then counts the articles published over the last 12 full months (UTC), per month, per section, per language, and how many articles were updated. Works with any CMS. **What is counted.** Only articles, dated by the publication date the site itself shows, read in this order: structured data (JSON-LD `datePublished`), meta tags, an `itemprop` attribute, a labelled date in the visible text such as "Published on" or "Publié le", the first line of a press release ("City, March 12, 2026"), then the first `<time>` element ("Updated on" is never a publication date). A page is an article when it is typed as one (JSON-LD Article, BlogPosting, NewsArticle and similar types, or an `article:published_time` meta tag), when its date comes from such a visible label or from the first line of a press release (no inference needed), or when it belongs to a section without article markup whose pages read are mostly dated by an `itemprop` attribute or a `<time>` element: that section is listed in `method.inferredSections` (the exact rule is described there) and its dated pages are counted (never its future dates, never an agenda or event section). Other dated pages are not counted, their number is returned as `publications.otherDatedPages`. Articles that share the same day are counted like any other: a section where at least 80% of the pages counted share one day is only reported in `method.sameDaySections` (grouped publication, or dates changed in bulk), never excluded. Pages read without any date are never counted, their number is returned as `method.undatedPages`; a page served but not HTML (a PDF) is one of them, not a failure in `method.pagesFailed`. An article republished with a new date counts as a publication. **Asynchronous, poll the result.** This call only starts the analysis and answers HTTP 202 with an `analysisId` and a

Find the representative pages of a website from its sitemaps, before generating a persona brief (free tool) Reads the sitemaps of a website (declared in robots.txt, otherwise /sitemap.xml, /sitemap_index.xml and /wp-sitemap.xml) and returns up to 200 URLs of the same host, editorial pages first. The first URLs, as many as the URL limit of your tier, are flagged `suggested`: send them in `urls` to `POST /api/v1/tools/persona-brief`. Same tiers as the creation call, with their own daily counter per UTC day: 20 discoveries per day per IP address without an API key, 50 for a signed-in account, 200 with the API key of an account whose plan includes API access. A key whose plan does not include API access returns 401: remove the `Authorization` header to use the free anonymous tier. Quota headers: `X-RateLimit-Limit`, `X-RateLimit-Used`, `X-RateLimit-Remaining`, `X-RateLimit-Reset`. `Retry-After` is set on 429 and 503. A 400, 502 or 503 answer gives the consumed quota back; SERVICE_UNAVAILABLE consumes none. **Request format.** Send the body as JSON with `Content-Type: application/json`: any other content type returns 415. Without an `Authorization` header, a request sent by a web page of another site (an `Origin` other than the SERPmantics app, or `Sec-Fetch-Site: cross-site`) returns 403. Server-to-server calls send no `Origin` header and are not affected.

Read an AI persona and brand voice brief, poll until it is done Returns the brief started by `POST /api/v1/tools/persona-brief`. While `status` is `pending`, `fetching`, `analyzing` or `synthesizing`, call again every 3 seconds: `progress` and `pages` show what has been read so far. When `status` is `done`, `brief` holds the structured brief, `brief.writingPrompt` the ready-to-paste prompt and `markdown` the full document. When `status` is `failed`, `failureReason` says why (NO_USABLE_PAGE, LLM_UNAVAILABLE, TIMEOUT, INTERNAL). A page with a `failureReason` did not contribute to the brief. ANALYSIS_FAILED is the only one on a page that was read: it keeps its `title` and `wordCount`, stays counted in `progress.pagesFetched` and never enters `progress.pagesAnalyzed` nor `metrics`. No quota is consumed. The `briefId` is random: whoever holds it can read the brief, which is what makes share links work. Briefs expire after 90 days. Reads that are not attributed to an account are subject to three anti-abuse counters, all per IP address and per UTC day: the total number of requests, the reads of a single brief, and the number of different briefs read. All three are far above any legitimate polling, including the busiest paid account: crossing any of them returns 429 READ_RATE_LIMITED with `Retry-After`. Once the cost ceiling is reached, further requests keep being refused until it resets, whether or not they carry a valid briefId.

Generate an AI persona and brand voice brief from the pages of a website (free tool) Reads public pages of a website and produces an editorial persona and writing style brief: who writes, for whom, tone on 6 axes, vocabulary, structure, do and don't lists, verified quotes from the pages, style metrics measured on the text, and a ready-to-paste writing prompt for any AI writing tool (`brief.writingPrompt`, plus `brief.writingPromptCompact` of at most 1500 characters). **Asynchronous, poll the result.** This call only starts the job and answers HTTP 202 with a `briefId` and a `pollUrl`. Call `GET /api/v1/tools/persona-brief?briefId=...` every 3 seconds until `status` is `done` or `failed`. A brief takes about 80 seconds plus 5 seconds per page, rounded up to the half minute: about 2 min for 3 pages, 2 min 30 s for 10 pages. MCP clients must call the `get_persona_brief` tool again until the status is terminal. **Identical requests are reused for 72 hours.** The same set of URLs, in any order, with the same `outputLanguage` and the same `brandName`, returns the brief already computed instead of computing it again: HTTP 200 with `reused` true, `status` already `done`, the original `briefId` and `reusedCreatedAt`, the date of the brief it reuses. Nothing is created, and your daily quota is given back, so a reused answer costs you nothing. The pages of a reused brief are listed in the order of the original request, not in the order you just sent. Send `force` true to skip the lookup and compute a new brief, which answers 202 and consumes quota. **Addresses.** Duplicate URLs, compared once normalized, are read once. A private, local or blocked address is not refused by this call: the brief is created, and that page ends with `status` failed and `failureReason` BLOCKED_ADDRESS (the brief fails with NO_USABLE_PAGE when no other page could be read). **Tiers, per UTC day.** Every tier is capped at 10 URLs per brief since 21 September 2026. - Without an API key, free anonym

Get current API usage and quota status Returns the current period's API guide usage (guides created through the API or MCP), quota limit, remaining count and the renewal date. Aligned on the Stripe subscription billing cycle, or on the calendar month (UTC) for a Conqueror account without a subscription. Does not consume credits. `enforced` tells whether the quota is enforced on the current window: when `true`, a guide creation through the API or MCP that would exceed the limit is refused with HTTP 402 (see `POST /api/v1/guides`). When `false` (any plan other than Conqueror, a billing cycle that started before the refusal went live, or a Conqueror subscription in payment recovery, counted over the last 30 days with no reset date), the figures are informational only and nothing is refused on quota grounds. `upgrade_url` is the absolute link to the "Priority and API volume" add-on (the same as `details.upgrade_url` of the 402), absent when the add-on cannot raise the quota (already at its highest volume, or account without a subscription to add it to).

无需输入参数。

Grand-livre crédits d'un compte (admin) Timeline complète et immuable des mouvements de crédits d'un utilisateur (octrois, consommations, refunds, resets, ajustements admin), avec libellés FR en clair, delta signé, solde après, source, auteur et référence. Inclut le solde reconstruit à une date arbitraire (paramètre `at`) et un contrôle de cohérence (solde == dernier balanceAfter == somme des deltas). Réservé aux administrateurs. Lecture seule.

Get data for a specific guide Retrieves details of a specific guide. While the guide is being created, the endpoint returns 202 (poll again later). If the creation failed permanently (explicit terminal flag, or a failure older than 15 minutes with no retry left, see progressStatus.terminalInferred), it returns 200 with success=false, status=failed, a human-readable French error message, creationFailed=true, refunded (whether the consumed credits were automatically given back) and guide.progressStatus (raw reason, message, terminal, kind, and failureFacts when the figures are known, which is only possible for sources whose web pages we read, that is a search engine or a `_CITATIONS` source, never a source in answer mode). Stop polling in that case.

Update a guide Updates editable fields of a specific guide (group, status, share state, linked URL, meta, hidden expressions). Only owners may update.

Delete a guide Deletes a specific guide. Deliberately NOT blocked by the 180-day expiry: an expired guide can no longer be read, but it can always be deleted, so that you can still clean up your account.

List user's guides Returns a list of guides for the authenticated user. Use `query` to check whether a guide already exists before creating one (creating a duplicate costs credits). Beware of two behaviours of this endpoint: - `query` and `group` are case-insensitive REGULAR EXPRESSIONS, not exact matches: special characters in the value are interpreted as regex syntax, and an invalid expression is searched as typed. (`status` is different: a known status is matched exactly, any other value falls back to a regex.) Always compare the returned `query` and `source` yourself, and fall back to an unfiltered paginated scan before concluding that nothing exists; - `totalCount` does NOT take `query` nor `group` into account (known limitation: both are applied as application-level regexes that the count query does not know, so it returns 0 as soon as either is used, alone or combined with `status`). Filtering on `status` alone does give a correct `totalCount`, since it is a real stored field. For an existence check, trust the `guides` actually returned; `totalCount` is only reliable for paginating a listing filtered by `status` alone, or not filtered at all. An empty result is returned as a 404 with `success: false` and `error: "No guides returned"`, not as an empty list.

Create new guides Create one or more new guides based on provided queries. Each guide targets exactly ONE engine and ONE analysis mode, chosen with the optional `source` field (default `google`). How to request each guide type: 1. Google SERP guide (1 credit per guide): omit `source`, or pass `source: "google"`. Example payload: {"queries": ["best crm"], "lang": "en-us"} 1bis. Google AI Overview guide (1 credit per guide). Two modes, like AI engines: `source: "google_ai_overview"` builds the guide from the TEXT of Google's AI answers (AI Overview, completed with AI Mode answers) ; `source: "google_ai_overview_citations"` builds it from the content of the web SOURCES those answers cite (recommended for GEO). Same language/country parameters as a Google SERP guide, 1 credit per guide in both modes. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "google_ai_overview_citations"} 2. LLM ANSWER guide (4 credits per guide): pass the engine name alone, e.g. `source: "chatgpt"`. The guide is built from the answer text the AI generates for the query. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt"} 3. LLM CITATIONS guide (4 credits per guide) [RECOMMENDED AI mode]: pass the engine name with the `_citations` suffix, e.g. `source: "chatgpt_citations"`. The guide is built from the content of the web pages the AI cites in its answer. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt_citations"} Which AI mode to pick? For GEO (getting a page visible in AI answers), prefer `<engine>_citations`: AI engines send traffic by CITING pages as sources, so the winning move is to look like the pages they cite. The answer-text mode (`<engine>` alone) is mostly useful to analyze how the AI phrases its own answer. When in doubt, pick `<engine>_citations`. The same two modes exist for every AI engine (chatgpt, perplexity, claude, gemini, grok, mistral, deepseek). To optimize the

Delete multiple guides Deletes multiple guides at once

无需输入参数。

Analyze content optimization score Analyzes the optimization score of the provided content for a specific guide MCP channel defaults: this tool sends scoreProgressive=false, includeEmbedding=false when you leave them out. That is specific to this channel and overrides the default documented on those parameters, which describes the REST API. What it changes in the response: with scoreProgressive=false, contentAnalysis.progressiveScores comes back empty ({}); with includeEmbedding=false, contentAnalysis.embeddingAnalysis is omitted from the response. Set a flag to true in your arguments to get its content back; any value you do pass is sent unchanged, including false. The whole response is handed to the model, and this is where most of its size goes, so it is opt-in on this channel: ask only for what you are going to read.