OtterlyAI
Connect OtterlyAI to track how your brand shows up in AI search, see which pages get cited, read the answers themselves, and audit your site.
You end up with a single OtterlyAI API key, prefixed oai_live_, that you paste into PopMCP's API key field.
Paid plan required before this connector works
OtterlyAI only lets accounts on the Standard, Premium, or Custom/Enterprise plan create an API key - the entry-level Lite plan has no API at all. There is no review or application, only the plan gate.
- Typical wait
- None - a key is generated instantly once the account is on a qualifying plan.
- Cost
- Otterly's public pricing page lists Standard at US$189/month and Premium at US$489/month (US$160 and US$422/month billed annually, a 15% annual discount). Lite at US$29/month does not include API access. Enterprise is custom, quoted from about US$1,000/month.
- Blocked until approved
- The entire Public API: no Bearer token can be minted on Lite, so every endpoint is unreachable - reading prompts, AI search results, citations, brand mentions and share-of-voice, and the write operations (running GEO Audits on demand, creating or deleting prompts and tags).
- Works meanwhile
- OtterlyAI offers a free trial for new users, which is the cheapest way to reach a real key - but Otterly does not document whether API access is enabled during the trial, so confirm it before planning around it. Otherwise there is no unauthenticated surface to build against; the connector cannot be exercised at all below Standard.
Where to apply: No application or review. In the OtterlyAI dashboard go to Settings > API Keys > Create API key, choose the workspace(s) and read-only vs read-and-write permission, and copy the key.
- The key is displayed exactly once - 'You will only see it once' - and is not recoverable afterwards.
- A read-only key returns 403 on audit, prompt, and tag write endpoints; pick read-and-write up front if the connector needs to trigger audits.
- Keys are scoped to selected workspaces, so a multi-brand account may need one key per workspace.
- Monthly request caps apply on top of the plan gate: 2,000 requests/month on Standard and 5,000 on Premium, after which calls return 429.
- Some AI engines are sold as add-ons rather than core plan features, so data for those engines can be missing from API responses even on a paid plan.
- Setup time
- 3 min
- Auth
- API credentials
- API base URL
- https://data.otterly.ai/v1
- Rate limits
- OtterlyAI meters Public API requests against your plan's per-period allowance and returns 429 once you exceed it. The account endpoint and the Usage tab report current consumption and limits.
Before you begin
- OtterlyAI account on a paid plan or an active free trial
- The Admin role on the OtterlyAI account. Only admins can create, rotate or revoke API keys
- Access to the workspaces whose brand reports you want PopMCP to read
Get your credentials
Sign in to the OtterlyAI dashboard
Go to app.otterly.ai and sign in with an account that holds the Admin role.
Open Admin → API Keys
In the left menu open Admin and click API Keys. The direct link is app.otterly.ai/api-keys.
API Keys
Create, rotate and revoke keys for the OtterlyAI Public API.
| Name | Key | Workspaces | Access | Status | Created |
|---|---|---|---|---|---|
| Looker exportdana@acme.com | oai_live_****9f21 | Acme Brand | Read | Active | Mar 4, 2026 |
| Old Zap keysam@acme.com | oai_live_****1c07 | Acme DACH | Read & write | Revoked | Jan 11, 2026 |
API Keys sits under Admin in the left menu.
Create the key and pick its workspaces
Click Create API key, name it PopMCP, tick every workspace PopMCP should read and set the access level to Read. Click Create key.
API Keys
Create, rotate and revoke keys for the OtterlyAI Public API.
A key with no workspace ticked returns 403 on every report endpoint.
Copy the key into PopMCP
Click Copy and paste the value into PopMCP's API key field before you close the dialog.
API Keys
Create, rotate and revoke keys for the OtterlyAI Public API.
Lose the key and you rotate or revoke it, there is no way to reveal it again.
Connect in PopMCP
Open your workspace, choose OtterlyAI in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| API keysecret | OtterlyAI dashboard (app.otterly.ai) → Settings → API Keys → Create API key. Pick the workspaces it may read and whether it gets read or read and write, then copy the key. It is shown only once. Stored encrypted and used server side only.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against OtterlyAI immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
PopMCP shows the connection as Connected and the workspace picker lists the OtterlyAI workspaces you granted. Asking for your brand reports returns real report names rather than an empty list.
Troubleshooting
401 Unauthorized
Why: The key was mistyped, truncated on paste, or revoked in OtterlyAI.
Fix: Re-copy the key, checking it starts with oai_live_, or create a new one at app.otterly.ai/api-keys.
The key is no longer on screen
Why: OtterlyAI shows the full secret once, at creation.
Fix: Rotate or revoke the key on the API Keys page and create a replacement, then paste the new value into PopMCP.
403 Forbidden
Why: The access level is too low, or the workspace you are querying was not ticked when the key was created.
Fix: Create a new key with Read access and every workspace PopMCP needs selected.
The API Keys page is missing
Why: You are signed in as a workspace member rather than an account admin.
Fix: Ask an OtterlyAI account admin to create the key, or have them grant you the Admin role.
429 Too Many Requests
Why: Your plan's Public API allowance for the current period is used up, or requests are arriving too fast.
Fix: Wait and retry. Check the Usage tab on the API Keys page for current-period consumption and upgrade the plan if you keep hitting the ceiling.
Reports come back empty
Why: The key is valid but scoped to a different workspace than the brand you are asking about.
Fix: Check the Workspaces column on the API Keys page and create a replacement key that covers the right one.