Pricing, limits, and integration
API access requires a paid plan; there is no free tier and no public pricing, since Business, Enterprise and Managed Service are all quoted via demo. Once you are on a plan, keys are created self-serve in Settings > API with read, write and export scopes, optionally restricted to specific projects. Keys are shown once and stored hashed, so treat them like any production secret.
Rate limits are published rather than hidden, which I wish were the norm: the documented ladder runs from 60 requests a minute and 5,000 a day at the entry level to 120/minute and 25,000/day on Business, 300/minute and 100,000/day on Agency and 600/minute and 200,000/day on Enterprise. Exceeding a limit returns a 429 with a Retry-After header. One honesty note: the docs' rate-limit tables still name Creator and Agency plans that no longer appear on the public pricing page, so confirm your actual tier's limits on the demo.
For an agent build, the practical pattern: use the MCP server for conversational, read-side work (visibility trends, competitor rankings, source analysis inside Claude or Cursor), and the REST API with a write-scoped key for automation (adding tracked prompts, managing projects and tags, submitting attribution data, bulk-exporting tracking history into your warehouse). The markdown docs plus llms.txt mean your agents can read the reference natively.
How much does the Finseo API actually cost?
Finseo 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 appear as a line item in the pricing comparison table under reporting and extensibility. Which plans include them is not spelled out publicly, so confirm webhook availability for your tier on the demo.
Which AI clients can read Finseo data?
Not every AI assistant supports MCP natively. Here's the per-client picture for Finseo specifically.
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Native MCP | Documented setup: add the server URL https://api.finseo.ai/v1/mcp with an Authorization: Bearer header using a read-scope API key. |
| Claude Code | Native MCP | Same remote HTTP MCP server; add it as an HTTP server with the Bearer header. |
| Cursor | Native MCP | Documented setup guide in the Finseo docs (docs.finseo.ai/mcp/cursor). |
| ChatGPT | Via connectors | The pricing page lists GPT among supported MCP clients; there is no dedicated setup guide in the docs yet. |
| n8n | API-only (custom code) | n8n is listed among Finseo's 22 native integrations, and the REST API covers the same data for custom nodes. |
Finseo also has an MCP server
If you're wiring Finseo into Claude / Cursor / Codex, the MCP server is usually less code than the REST API.
See Finseo MCP pageWhat you can build with the Finseo API
Three personas, three different shapes of build. Pick the row that matches how you actually ship.
Glue Finseo into your daily workflow
- Pull a digest of fresh activity into your morning Slack
- Trigger a one-off backfill when something looks off
- Pipe data into your own SQLite for ad-hoc queries
Sell Finseo reporting at scale
- White-label Finseo data into client-branded dashboards
- Run scheduled multi-account reports without logging into the Finseo UI
- Cross-reference with the rest of the client's stack (CRM, analytics, ad spend)
Production pipelines for Finseo
- Real-time sync into your warehouse via webhooks
- Custom alerts the dashboard's built-in alerting can't express
- Backfill + idempotency handling for Finseo data older than the dashboard exposes
Quickstart template
# Starter template — endpoint paths and SDK package names come from # the Finseo API docs: https://docs.finseo.ai curl -X GET "https://api.finseo.ai/<your-endpoint>" \ -H "Authorization: Bearer $YOUR_API_KEY" \ -H "Accept: application/json" | jq .
Template only. Endpoint paths, exact base URL, and auth header format come from docs.finseo.ai.
Limits and gotchas
- OpenAPI is published — auto-generated clients work out of the box. Saves writing wrappers by hand.
- Webhooks available — react to Finseo 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.
- Structured JSON outputs — agent-friendly, no scraping required.
- No-code fallback: Zapier cover the common triggers if you want to skip writing API code for simple flows.
Agent-readiness verdict
A well-executed API for the GEO category: OpenAPI 3.1 spec, scoped keys, published rate limits, bulk export and markdown docs with llms.txt. It loses points only on access, since keys require a paid plan and every plan is demo-gated. That lands it at 8 out of 10.
Official remote MCP server (api.finseo.ai/v1/mcp, Bearer key, 7 read tools for projects/metrics/prompts/competitors/sources/tags/fanouts) plus a documented REST API with OpenAPI 3.1 spec, scoped API keys (read/write/export), published per-plan rate limits and llms.txt on both site and docs. Held back from higher: API keys require a paid, demo-gated plan (no self-serve signup) and the MCP surface is read-only.
Finseo API FAQ
Does Finseo have a public API?+
What auth does the Finseo API use?+
Is there an OpenAPI / Swagger spec I can auto-generate clients from?+
Does Finseo support webhooks?+
Should I use the API or the MCP server for Claude / Cursor / Codex?+
Sources
- Finseo official site: https://www.finseo.ai
- API docs: https://docs.finseo.ai
- OpenAPI spec: https://docs.finseo.ai/openapi.yaml
- MCP server: https://docs.finseo.ai/mcp/overview
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.