Skip to main content
3RD’s data doesn’t have to stay in the dashboard. The Export API feeds your reporting stack; the MCP endpoint lets AI tools query your data conversationally.

​
Two key families

Which key you need depends on what you are building. They are not interchangeable. Sending one where the other belongs returns 401.

​
Managing keys

From either tab you can:
  • Create and label keys per integration or script, so you always know what a key is for
  • Revoke any key instantly
  • Rotate keys periodically, like any credential

​
Copy your key when it’s created

When you create a key, 3RD shows the full value once in a reveal dialog with a Copy button. Copy it and store it somewhere safe (a password manager, your CI/CD secret store, or your integration’s config) — the reveal dialog is the only place either tab surfaces the key.
Lost or leaked a key? Revoke it and create a fresh one — revoking takes effect immediately.
Treat API keys like passwords: never commit them to a repository or share them in plain text. Label each key by use, so revoking one doesn’t break something else.

Export API reference

Endpoints, parameters, response formats, and an OpenAPI specification your integration team can import.

​
MCP

The MCP endpoint exposes your 3RD data through the Model Context Protocol — the open standard that lets AI assistants query external tools. Connect an MCP-capable client and ask questions about your visibility right from the assistant:
“How did our visibility on Must-Win prompts develop in the German market this month?”

MCP documentation

What the connector can access, example queries, and step-by-step setup for Claude and Claude Code — in the MCP tab.