Overview

SEORCE API Reference

The SEORCE API lets you programmatically access your AI visibility data, integrate GEO analytics into your own dashboards, and build white-label reporting for your clients. The API is REST-based, returns JSON, and uses Bearer token authentication.

The API is currently in v1.0.0. The AI Beacon GEO endpoint is live and production-ready. Additional endpoints for Keyword Explorer, Content Studio, Technical Suite, Rank Tracker, and Web Analytics are in development and will ship throughout 2026. API tokens are available on Growth and Enterprise plans — contact support@seorce.com to request access.

Auth

Authentication

All API requests require authentication using a Bearer token in the Authorization header. Your token is provisioned by SEORCE and does not expire. Tokens are scoped to your account and carry access to all projects and prompts within it.

Header	Value	Required
Authorization	Bearer <your-token>	Yes — all requests
Content-Type	application/json	Yes — all requests

Never expose your API token in client-side code, public repositories, or frontend bundles. If a token is compromised, contact support@seorce.com immediately for rotation.

Endpoints

Base URL & versioning

All API endpoints are served from the base URL below. The version prefix is part of every endpoint path. When we release breaking changes, we increment the version number and maintain the previous version for a deprecation window.

https://api3.seorce.com/api/v1

Version	Status	Notes
v1	Active	Current production version. All new development.

Errors

Error codes

The API uses standard HTTP status codes. All error responses return a JSON body with a status and message field.

Status	Code	Meaning
200	OK	Request succeeded. Response body contains requested data.
400	Bad Request	Malformed request — missing parameters or invalid format.
401	Unauthorized	Missing or invalid Bearer token. Check your Authorization header.
404	Not Found	The requested resource does not exist.
429	Too Many Requests	Rate limit exceeded. Reduce request frequency.
500	Server Error	Unexpected server error. If persistent, contact support.

All error responses follow this structure:

"status": "error",
"message": "Human-readable description of what went wrong"

Limits

Rate limits

There are currently no hard rate limits enforced on the API. However, we ask that you use it responsibly and implement caching where appropriate. We reserve the right to introduce rate limits with reasonable notice as usage scales.

Current rate limitNone enforced

Recommended cache TTL5 – 60 minutes

GEO data updates periodically, not in real time. Caching responses for 5–60 minutes reduces load and improves your application's response time significantly. Future rate limits will be announced with at least 30 days' notice.

AI Beacon · GEO API

White Label GEO API

The GEO API provides programmatic access to all your AI Beacon data — brand mentions, citation positions, and LLM-level tracking across all your projects and prompts. Designed for agencies who need to embed AI visibility analytics into their own client dashboards.

White label use. This API is designed for agencies building branded client portals. All data is scoped to your SEORCE account. You present the data under your own brand — SEORCE is never exposed to your clients unless you choose to.

Supported LLM platforms

The API returns data for any platform that has at least one completed run. Current supported platforms:

ChatGPT

Claude

Gemini

Perplexity

Meta Llama

Grok

DeepSeek

AI Beacon · GEO API

List all projects

GEThttps://api3.seorce.com/api/v1/geo/white-label/projectsAuth required

Retrieves all projects for the authenticated account, including all prompts and their LLM data across every platform. This is the primary endpoint — most integrations only need this one call.

Response — project level

Field	Type	Description
project_id	string	Unique identifier for the project
domain	string	Domain name associated with this project
prompts	array	Array of prompt objects. See prompt-level fields below.

Response — prompt level

Field	Type	Description
prompt_id	string	Unique identifier for the prompt
prompt_text	string	The full question or prompt text being tracked
created_at	string (ISO)	Timestamp when the prompt was created
llm_data	object	Keyed by platform name. Contains mention and position data.

Response — per LLM platform (inside llm_data)

Field	Type	Description
is_mentioned_in_latest_run	boolean	Whether the brand was cited in the most recent run
position_in_latest_run	number \| null	1-based citation position in the latest run. null if brand not mentioned.
total_mentions	number	Count of runs where the brand was mentioned
run_count	number	Total number of runs executed

Position is 1-based. Position 1 means your brand was cited first in the LLM's response. Lower is better. A null position means the brand was not mentioned in the latest run — check total_mentions for historical presence.

AI Beacon · GEO API

Get single project

GEThttps://api3.seorce.com/api/v1/geo/white-label/projects/{project_id}Auth required

Retrieves a single project by its ID, including all prompts and LLM data for that project only. Useful when your integration already knows the project ID and you want to avoid fetching all projects.

Path parameters

Parameter	Type	Description
project_id	string	The project ID to fetch

AI Beacon · GEO API

Get prompt detail

GEThttps://api3.seorce.com/api/v1/geo/white-label/projects/{project_id}/prompts/{prompt_id}Auth required

Retrieves data for a single prompt within a project. Returns full LLM data for all platforms for that specific prompt only.

Path parameters

Parameter	Type	Description
project_id	string	The parent project identifier
prompt_id	string	The specific prompt identifier to retrieve

Guidance

Best practices

Cache responses

GEO data updates periodically rather than in real time. Cache responses for 5–60 minutes to improve your app's response speed and reduce unnecessary API calls.

Handle errors gracefully

Always implement error handling for network timeouts, 401 responses (token issues), and 500 errors. Use exponential backoff for retries on transient errors.

Protect your token

Never expose your Bearer token in client-side code or public repos. Use environment variables and server-side API calls. Contact support@seorce.com immediately if a token is compromised.

API support

support@seorce.com

For token requests, API questions, or data structure issues

Last updated March 2026 · API Version 1.0.0