All requests to the Supersonic MCP server require a valid API key. Keys are scoped to a single workspace and inherit the permissions of the user who created them.Documentation Index
Fetch the complete documentation index at: https://docs.supersonic.cv/llms.txt
Use this file to discover all available pages before exploring further.
API Keys
Pass your key in theAuthorization header:
Creating Keys
- Go to supersonic.cv/keys
- Navigate to Settings > Developers > API Keys
- Click Create Key
- Choose a name and select scopes
- Copy the key — it’s only shown once
API keys are per-workspace. If you have access to multiple workspaces, create separate keys for each.
Scopes
Restrict what a key can access by selecting tool categories:| Scope | Tools |
|---|---|
objects | objects.* |
records | records.* |
lists | lists.* |
views | views.* |
notes | notes.* |
tasks | tasks.* |
analytics | analytics.* |
reports | reports.* |
timeline | timeline.* |
graph | graph.*, contacts.classify |
integrations | integrations.* |
email | email.* |
messages | messages.* |
meetings | meetings.* |
billing | billing.* |
support | support.* |
Role-Based Access
API keys inherit the role of their creator:| Role | Access |
|---|---|
| Owner | Full access to all tools and workspace settings |
| Admin | Full access to all tools, cannot modify workspace settings |
| Member | Read access to all data, write access scoped to assigned records |