REST API

The SearchFIT API

Your AI visibility, content and search data over REST at api.searchfit.ai. Pull it into your own dashboards and publish from your own workflows.

api.searchfit.ai
# Every endpoint your credential can call
curl https://api.searchfit.ai/v1/tools \
  -H "Authorization: Bearer sf_your_key_here"

# A brand's AI visibility
curl https://api.searchfit.ai/v1/brands/{brand_id}/visibility \
  -H "Authorization: Bearer $SEARCHFIT_TOKEN"

# Publish an article to a connected platform
curl -X POST https://api.searchfit.ai/v1/content/{content_id}/publish \
  -H "Authorization: Bearer $SEARCHFIT_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "integration_id": "{integration_id}" }'
What you can build

Your growth data, in your own tools.

Pull visibility and search data into dashboards and reports, and publish from your own workflows.

AI visibility

Tracked prompts, scans across AI engines, visibility and competitors.

GET /v1/brands/{brand_id}/visibility

Content and publishing

Create and edit articles, then publish them to your connected platforms.

POST /v1/content/{content_id}/publish

Search performance

Search Console clicks, impressions and positions, beside keywords and backlinks.

GET /v1/brands/{brand_id}/search-performance

Webhooks

Register a URL and receive signed event deliveries in your own pipeline.

POST /v1/brands/{brand_id}/webhooks
Authentication

Two credentials, one header.

Every request sends Authorization: Bearer. Pick the credential that fits the job.

OAuth token

Sign in with your SearchFIT account. Best for your own scripts and internal tools.

  • Every endpoint your account can use
  • Covers anything outside an API key's scopes
  • The same sign in the MCP server uses

API key

A long-lived sf_ key for software that runs without a user present, such as a site that reads your articles.

  • Created for one brand
  • Reads published content only, unless you select more scopes
  • Endpoints outside its scopes answer 403
  • Can be pinned to your site's origin
Read published content with an API key
curl https://api.searchfit.ai/v1/brands/{brand_id}/content \
  -H "Authorization: Bearer sf_your_key_here"
103 endpoints

One catalogue, REST and MCP.

The API and the MCP server are built from the same 103 tools in 9 groups, so anything your agent can do, your code can too.

27

SEO and search performance

Keywords, competitors, Search Console performance, backlinks and GA4.

21

Technical SEO and media

Site pages, technical audits and the media library.

18

AI visibility tracking

Tracked prompts, scans across AI engines, visibility, competitors and sentiment.

18

Content

Articles and drafts: create, edit, generate, translate and publish.

8

Social listening

Reddit threads where your brand is discussed, and a drafted reply.

4

Browse the web

Read public pages in a fresh browser. Nothing is clicked or typed.

3

Brands

Brands and their setup. Every other tool starts from a brand id.

3

Webhooks

Register a URL to receive signed event deliveries.

1

Connectors

Connected integrations and publishing targets. Credentials are never returned.

Frequently asked questions

Read your AI visibility, tracked prompts, content, keywords and search performance, and act on them: run scans, create content and publish it to connected platforms. It is the same catalogue the MCP server exposes.

Send a bearer token. An OAuth token from signing in reaches every endpoint your account can use. An sf_ API key is scoped to one brand: a new key reads published content only, unless you select more scopes when you create it.

Every plan includes a monthly allowance of API calls, and the allowance grows with the plan.

Yes. A request over the limit gets a 429 response with a Retry-After header saying when to try again.