Spiderlook API
The Spiderlook API returns organization details, the companies you track (your brand, rivals, and benchmarks), Meta and Google ads, social posts, website changes and page-change history, and battlecards. To work with that data inside ChatGPT, Claude, Gemini, Cursor, Notion, PostHog and any other client that supports MCP, connect Spiderlook via MCP.
Open the API reference · Download OpenAPI JSON
How do I authenticate?
Send a bearer token on every request with the Authorization header.
Create and revoke tokens in the Spiderlook app under Settings, then Integrations. Use HTTPS only. Treat every token like a password: do not commit it to source control or share it in chat.
Authorization: Bearer <token>
Which token types are there?
Personal access tokens start with crpat_ and belong to the signed-in user who created them. Create and revoke them in Settings, then Integrations.
Organization API keys start with crorg_ and belong to the Organization. Organization admins create and revoke them in Settings, then Integrations. Requests authenticate as the organization key (a service identity), not as the person who created the key, so keys keep working if that person leaves the Organization.
Both credential types use the same permission and scope model on the public /v1 API.
Which scopes can a token have?
Tokens declare scopes that limit what the API can do. The current public scope is intel:read, which allows reading competitive intelligence for Organizations you can access.
Request only the scopes you need. Revoke a token in Settings, then Integrations when a person leaves or a script is retired.
Where is the full endpoint reference?
The interactive reference lists the public endpoints, request parameters, and response schemas from the live OpenAPI document. The API is versioned under /v1.