SearchChampFeature coverage
Understand which SearchChamp features are available through REST, MCP, or only in the SearchChamp app.
SearchChamp has three different integration surfaces. They do not expose the same capabilities:
- The public REST API is a stable, API-key-authenticated reporting surface with four read-only endpoints.
- The MCP connector gives compatible AI clients a broader, permission-scoped tool catalog.
- The SearchChamp app contains product workflows that are not yet public integration contracts.
Do not call app endpoints as a public API
An endpoint used by the SearchChamp web app is not automatically a public endpoint. Internal routes can require a browser session, use different authorization rules, and change without public API versioning. Only routes under the documented /v1/api/* surface are supported for API-key integrations.
Capability map
| Feature | Public REST API | MCP connector | SearchChamp app |
|---|---|---|---|
| Rankings | GET /v1/api/rankings | get_rankings, get_rank_movers, get_volatility | Full rank-tracking workflow |
| Tracked keywords | GET /v1/api/keywords | get_tracked_keywords | Keyword management and research workflows |
| AI Visibility | GET /v1/api/ai-visibility/summary for the latest summary | get_ai_visibility, get_bot_access_report | Prompt setup, scans, engine analysis, and management |
| Site audits | GET /v1/api/audit-issues for scores and issue counts | get_audit_summary, get_audit_issues, get_page_recommendations | Full audit runs, findings, and remediation workflow |
| Content Writer | No public REST route | Read drafts and article content; inspect recommendations and brand voice; use scoped publishing tools | Create and edit articles, configure generation, and manage the full writing workflow |
| Research Studio | No public REST route | ask_atlio can answer grounded questions and propose supported actions, but it does not start a Research Studio session | Start and manage full research sessions |
| Opportunities and backlinks | No public REST route | get_opportunities, get_backlinks_summary | Full opportunity and backlink workflows |
| Daily brief and site overview | No public REST route | get_daily_brief, get_site_snapshot | Full dashboards and briefs |
| Action Inbox | No public REST route | list_actions, approve_action, and decline_action with the required scope and role | Full action review and execution workflow |
| Publishing and site changes | No public REST route | Scoped article-publishing, custom-site publication, llms.txt, and approved-change tools | Full CMS and site-change workflows |
The MCP tool reference lists the exact tools, inputs, outputs, scopes, plan requirements, and availability. A capability named in the app column is not available to an external integration unless the REST or MCP column also names a supported route or tool.
Content Writer: what external clients can do
MCP clients can work with content that already exists in SearchChamp:
- Discover drafts with
get_content_draftsorlist_draft_articles. - Read a complete draft with
get_article_content. - Read rewrite guidance with
get_page_recommendationsand the configured voice withget_brand_voice. - Publish through
start_publishandreport_publishwhen the calling agent performs the external write. - Use
publish_articlewhen the connection, scope, role, plan, and server-side enablement allow SearchChamp to run its standard publisher.
Creating a brand-new Content Writer article is not currently a public REST operation or a dedicated MCP tool. Use the SearchChamp app to start article generation.
Research: what external clients can do
ask_atlio provides natural-language, tenant-scoped assistance over SearchChamp data. It can return grounded answers and propose supported actions, but it is not a public Research Studio session API. Starting a deep research session and managing its sources or report lifecycle currently requires the SearchChamp app.
AI Visibility: what external clients can do
Use the REST summary endpoint for reporting integrations that need the latest score, prompt counts, appearance rate, and share of voice. Use MCP for an AI client that needs the AI Visibility read plus related bot-access, site-snapshot, opportunity, or recommendation context. Creating prompts, changing engine configuration, and launching scans remain app workflows.
Why the surfaces differ
Public REST routes are long-lived contracts: they need versioned payloads, API-key authorization, tenant isolation, rate limits, metering, error semantics, and compatibility guarantees. SearchChamp exposes the smaller reporting surface today rather than presenting internal application routes as stable public APIs. MCP has a broader catalog because every tool declares its own schema, permission class, plan rules, and execution safeguards.
If your integration only needs data export or reporting, use the REST endpoint reference. If an AI client needs richer SearchChamp context or approved workflows, use the MCP documentation.