Pricing, limits, and integration
The API is not priced separately. It is a feature line on a plan, and Aiso lists "API access" on the Enterprise tier for brands, which is custom-quoted. The self-serve brand plans (Starter $19/month, Pro $215, Advanced $445, or $16, $183 and $378 billed yearly) cover the dashboard product and the hosted MCP server, but not the REST API.
On the agency ladder the same line appears from Scale at $705 a month ($599 billed yearly) and on the custom Comprehensive tier. If you want programmatic access at a published price rather than through a sales conversation, agency Scale is the only way to get it.
Default limits are 10 requests a minute and 20 a day per key, which Aiso can raise on request, with response headers to manage retries. There are no SDKs and no webhooks. If none of that fits, the official Apify actor is still there: about $10 per successful analysis returning 10 to 20 real conversations for a domain, billed through Apify with no charge when nothing relevant is found, and no Aiso tier requirement.
How much does the Aiso API actually cost?
Aiso publishes an API, but per-tier gating wasn't extracted automatically.
- Most likely scenario: API access is either included in all paid plans, or it's gated to higher tiers and we need to verify on the live docs page.
- Until verified, treat the question "which plan unlocks the API" as open. Don't budget on the assumption it's free with the cheapest paid plan.
API at a glance
Which AI clients can read Aiso data?
Not every AI assistant supports MCP natively. Here's the per-client picture for Aiso specifically.
| Client | Support | Notes |
|---|---|---|
| n8n | Via connectors | Call the REST API over HTTP, or the MCP server via n8n's MCP client node. No dedicated Aiso node. |
| Claude Code | Native MCP | Remote MCP at app.getaiso.com/api/v1/mcp, x-api-key header, no local install. Needs Enterprise or agency Scale. |
| Claude (Desktop/Web) | Native MCP | Named in Aiso's own setup docs. Remote HTTP MCP, so no local server to run. |
| Cursor | Native MCP | Named in Aiso's setup docs. Older stdio-only builds can bridge with mcp-remote. |
| ChatGPT | API-only (custom code) | No native connector. Reach it through the REST API in a custom integration. |
Aiso also has an MCP server
If you're wiring Aiso into Claude / Cursor / Codex, the MCP server is usually less code than the REST API.
See Aiso MCP pageWhat you can build with the Aiso API
Three personas, three different shapes of build. Pick the row that matches how you actually ship.
Glue Aiso into your daily workflow
- Pull a digest of ranking changes into your morning Slack
- Trigger a one-off backfill when something looks off
- Pipe data into your own SQLite for ad-hoc queries
Sell Aiso reporting at scale
- White-label Aiso data into client-branded dashboards
- Run scheduled multi-account reports without logging into the Aiso UI
- Cross-reference with the rest of the client's stack (CRM, analytics, ad spend)
Production pipelines for Aiso
- Real-time sync into your warehouse on a cron
- Custom alerts the dashboard's built-in alerting can't express
- Backfill + idempotency handling for Aiso data older than the dashboard exposes
Quickstart template
# Starter template — endpoint paths and SDK package names come from # the Aiso API docs: https://www.getaiso.com/docs curl -X GET "https://www.getaiso.com/<your-endpoint>" \ -H "Authorization: Bearer $TOKEN" \ -H "Accept: application/json" | jq .
Template only. Endpoint paths, exact base URL, and auth header format come from getaiso.com/docs.
Limits and gotchas
- No OpenAPI spec — you write typed clients by hand or use a third-party generator on the docs HTML.
- No official SDK detected. Plan on hitting the API directly with your HTTP client of choice.
- Rate limits: always read the docs page before scaling — the published limit is usually lower than the practical one and overages can be expensive.
Agent-readiness verdict
A documented first-party REST API covering projects, prompts, brands, snapshots and the brand, domain and URL reports, on a single account key. No SDKs, no webhooks, 20 requests a day by default, and unlike the MCP server it is still gated to Enterprise or agency Scale. 6 out of 10.
Solid agent fit, and the commercial catch has mostly lifted. Aiso runs an official hosted MCP server at app.getaiso.com/api/v1/mcp exposing 19 tools across projects, prompts, topics, brands, snapshots and its brand, domain and URL reports, plus a first-party REST API at app.getaiso.com/api/v1, both on one account API key sent as x-api-key. The MCP is remote HTTP, so Cursor and Claude Desktop connect with no local install, it accepts OAuth Bearer as well, and it is listed in Claude's connector directory. Since August 2026 hosted MCP access is included on every brand and agency plan, so the $19/mo Starter tier is the lowest paid price for MCP access in this category, beaten only by PromptWatch, which includes MCP on a free plan. Most tools read; create_project and add_prompts write, once per project. What keeps it level with Peec and Otterly rather than ahead: the REST API is still Enterprise for brands or the $705/mo agency Scale tier, keys default to 20 requests a day, and there are no SDKs and no webhooks.
Aiso API FAQ
Does Aiso have a public API?+
What auth does the Aiso API use?+
Should I use the API or the MCP server for Claude / Cursor / Codex?+
Sources
- Aiso official site: https://www.getaiso.com
- API docs: https://www.getaiso.com/docs
- MCP server: https://app.getaiso.com/api/v1/mcp
10+ years in digital marketing. I review marketing software for AI-stack fit: real pricing, MCP and API support, and how cleanly each tool drops into an AI agent workflow, cross-checked against verified data and real user feedback.