Pricing, limits, and integration
There is no separate price for the API, it comes with the platform, and there is the rub: AirOps publishes no plan prices. As of July 2026 the pricing page shows Solo, Pro and Enterprise as feature lists with Start for Free and Talk to Sales buttons, and the only dollar figure anywhere on it is the Solo overage rate of $0.025 per task. Billing is metered in tasks, which are consumed by specific workflow step types rather than every step, so a heavy API-driven workload spends against the same pool your team's manual runs use.
Two practical limits to plan around. First, tasks: 20,000 a month on Solo and 75,000 on Pro, with overage billed rather than blocked, so a runaway loop costs money instead of erroring. Each workspace also gets 50,000 free credits to exercise workflows before billing starts, and there is a 14-day free trial. Second, no published rate limits and no OpenAPI spec, so build in backoff and treat sustained high-frequency polling as something to test rather than assume.
How much does the AirOps API actually cost?
AirOps 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
Webhooks: Webhooks work in both directions. Inbound: a Playbook or Workflow can be started by an Incoming Webhook trigger, alongside Schedule, Monitor and AEO Insight triggers, and there is a documented Zapier trigger for the same job. Outbound: workspace monitoring can post failure alerts to Slack or an incoming webhook of your choosing. What is not documented is a general event bus for content or visibility changes, so treat webhooks as a way to start and supervise runs rather than to subscribe to every data change.
Which AI clients can read AirOps data?
Not every AI assistant supports MCP natively. Here's the per-client picture for AirOps specifically.
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Via connectors | Official AirOps Claude Connector in Claude's directory, with Interactive Apps so charts render in the conversation. |
| Claude Code | Native MCP | Vendor documents: claude mcp add --transport http airops https://app.airops.com/mcp, then /mcp to authenticate. |
| Cursor | Native MCP | Settings, Tools and MCP, New MCP server, then Connect to complete OAuth. |
| Windsurf | Native MCP | Settings, Cascade, MCP Servers, Add custom server with the app.airops.com/mcp URL. |
AirOps also has an MCP server
If you're wiring AirOps into Claude / Cursor / Codex, the MCP server is usually less code than the REST API.
See AirOps MCP pageWhat you can build with the AirOps API
Three personas, three different shapes of build. Pick the row that matches how you actually ship.
Glue AirOps 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 AirOps reporting at scale
- White-label AirOps data into client-branded dashboards
- Run scheduled multi-account reports without logging into the AirOps UI
- Cross-reference with the rest of the client's stack (CRM, analytics, ad spend)
Production pipelines for AirOps
- Real-time sync into your warehouse via webhooks
- Custom alerts the dashboard's built-in alerting can't express
- Backfill + idempotency handling for AirOps data older than the dashboard exposes
Limits and gotchas
- No OpenAPI spec — you write typed clients by hand or use a third-party generator on the docs HTML.
- Webhooks available — react to AirOps events in real time instead of polling.
- 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.
- No-code fallback: Zapier cover the common triggers if you want to skip writing API code for simple flows.
Agent-readiness verdict
A capable execution API held back by one open question: what it costs and who gets it. The surface itself is well shaped for automation, with real triggers, file handling and Grids, and webhooks that let you both start runs and catch failures in Slack. But there is no published SDK, no OpenAPI spec surfaced, and the plan comparison table puts API data export against Enterprise while AirOps publishes no prices at all. Design your integration on the assumption that you need to confirm tier access first.
AirOps API FAQ
Does AirOps support webhooks?+
Should I use the API or the MCP server for Claude / Cursor / Codex?+
Does AirOps have a public API?+
Sources
- AirOps official site: https://www.airops.com
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.