Skip to main content

Overview

Searchable exposes three programmatic surfaces. Pick the one that fits your use case:

MCP (AI assistants)

35 read-only tools for Claude, Cursor, and other MCP clients — the richest way to query your data.

REST API

Fetch audits & issues and generate shareable reports with an API key.

Ingest API

Send AI-bot traffic events from any language or platform.
API access requires a paid plan (Starter, Professional, or Scale). API keys can’t be created on the Free plan.

Authentication

Create an API key in Settings → Workspace → Integrations in your Searchable dashboard. Keys start with sea_ and are shown only once — store it securely. Send it as a Bearer token on every request:

Scopes

Each key carries one or more scopes. Read endpoints require read (the default); write endpoints require write. A key can also be bound to a single project. A project-bound key only works against that project; leave a key unbound to use it across all projects you can access.

Fetch audits + issues

Retrieve the latest audit per page, when each was last completed, and optionally the open issues for each page.

Generate a shareable report

Generate and publish a report, and get back its public share URL. This is a write action, so it isn’t an MCP tool — use this endpoint.
Requires the write scope and a plan that includes report sharing.

Query visibility, sources & sentiment

For visibility scores, share of voice, sources, sentiment, and GA4/GSC data, connect the MCP server — it exposes 35 read-only tools over the same data and handles auth for you. It’s the fastest path for read-heavy automation and works directly inside Claude, Cursor, and other assistants.

Send AI-bot traffic

To report request events from your own app or CDN (so crawlers like GPTBot and ClaudeBot show up in your dashboard), use the REST Ingest API. That endpoint uses a separate ingest key (sk_live_…) and a signed edge path — see its page for the full contract.

Error handling

API key best practices

Never commit API keys to version control — use environment variables
Scope each key to the minimum it needs (read unless it must write)
Bind a key to a single project when it only ever touches that project
Use separate keys for dev and prod, and rotate them regularly
Revoke compromised keys immediately in Settings → Integrations

Need more?

Higher rate limits, custom endpoints, or a dedicated integration? Contact support@searchable.com.

Next steps

MCP Integration

Connect Claude, Cursor, and other assistants to your Searchable data.

REST Ingest API

Send AI-bot traffic events from any stack.