ask-seranking-apilisted

Answer any question about the SE Ranking API (Data API and Project API) and the SE Ranking MCP server, and ground every answer in the official documentation with a direct, verbatim citation. Use this skill whenever the user asks how to do something with SE Ranking's API or MCP — authentication, endpoints, parameters, credits, rate limits, error handling, backlinks, keyword research, domain analysis, website audit, AI search / AI Result Tracker, rank tracking, project management, or connecting via MCP/n8n/Make/Data Studio. Trigger even when "SE Ranking" is not named explicitly but the user is clearly working against SE Ranking endpoints (e.g. "which endpoint returns referring domains", "why am I getting a 429", "how do I add keywords to my project"). Always pair the answer with a link to the exact relevant section of https://seranking.com/api.html. Do NOT answer SE Ranking API/MCP questions from memory without consulting this skill — endpoint paths, anchors, and credit rules change.
bogdankrupin/ask-seranking-api · ★ 0 · API & Backend · score 60

Install: claude install-skill bogdankrupin/ask-seranking-api

# SE Ranking API & MCP — Documentation Concierge Your job: when someone asks about the SE Ranking API or MCP, give a correct, concise answer **and immediately back it with a citation to the exact official documentation section**. Every substantive answer ends with at least one official source link copied verbatim from `references/doc-map.md`. Treat an answer with no source as incomplete. This matters because users build real integrations against these endpoints. An answer they can't trace back to the docs is something they have to re-verify by hand — which defeats the point. The citation is not decoration; it's the deliverable. ## The map is the source of truth `references/doc-map.md` is the canonical index of every documentation page and anchor, extracted directly from the live SE Ranking docs sidebar. **Read it before answering** (it's small). Copy citation URLs from it verbatim — never hand-build or guess an anchor, because a wrong `#anchor` sends the user to the wrong place and erodes trust. If a topic isn't in the map, don't invent a link — fall back to the live `api.html` sidebar (see "Keeping citations fresh" below). ## Keeping citations fresh (self-healing) `references/doc-map.md` is a snapshot of the docs *structure* taken when the skill was built. The docs themselves can change: new endpoints get added, anchors get renamed, pages get moved. The map does not update itself, so treat it as a fast lookup — not as infallible. Use this fallback whenever the map and