API & MCP
Your competitor intelligence, in the AI tools you use
A read-only REST API and an MCP server. Assistants like Claude, ChatGPT, Claude Code, Cursor and VS Code answer from what Orlea tracked for your workspace, and link every claim back to the change it came from.
14-day free trial · No card needed · Enterprise? Request a demo
Illustration with fictional companies and people.
How it works
Three steps, then it runs itself.
- 01
Create a key
An owner or admin makes one in Settings → API, named after where it will be used. It is shown once; Orlea keeps only a fingerprint.
- 02
Connect your tool
Add Orlea's server address to Claude or ChatGPT and sign in, give Claude Code, Cursor or VS Code the address and a key, or send the key with requests to the REST API.
- 03
Ask, or read
Your assistant calls Orlea's tools and answers with links to each change; your own code reads the same data as JSON.
Product tour
See the change behind an answer.
The API isn't part of the tour. What it returns is: step through one change as Orlea records it, the facts, the evidence and the interpretation kept apart, as an assistant reads and cites it.
Take the tour- 01What was detected
- 02Why it matters
- 03What changed
- 04The evidence
- 05Suggested responses
- 06Where it reaches you
For AI assistants
Connect once, then just ask.
Orlea's MCP server gives an assistant eight read-only tools. It decides which to call, and answers from your workspace with links back to each change, so you can check every claim.
Assistants that connect today
ClaudeSign in
On the web or in Claude Desktop: add a custom connector with the server address, then connect, sign in to Orlea and pick the workspace. On Claude's Team and Enterprise plans an owner adds the connector once and each person connects with their own Orlea account.
ChatGPTSign in
In developer mode, create a connector with the server address and OAuth, then sign in to Orlea and pick the workspace. Availability depends on the ChatGPT plan.
Claude CodeSign in or API key
One command in a terminal, then /mcp to sign in to Orlea in the browser. In scripts, send an API key as a header instead.
claude mcp add --transport http orlea https://app.orlea.com/api/mcpCursorAPI key
Add Orlea to ~/.cursor/mcp.json, or to a project's .cursor/mcp.json, with the key from your environment.
VS CodeAPI key
Add Orlea to .vscode/mcp.json. VS Code asks for the key once and keeps it in its secret storage.
The tools
- list_competitors
- The competitors you track
- get_competitor
- One competitor's pages and focus, by name, domain or id
- search_changes
- Changes by competitor, kind, priority, source and dates
- get_change
- One change with every evidence link
- get_latest_brief
- The newest weekly brief
- get_battlecard
- A competitor's battlecard as last written
- get_product_prices
- Price positions and moves, on Pro, Team and Enterprise
- ask_orlea
- A question answered from your history, with citations
Questions to ask_orlea are answered as Ask Orlea answers them in the app, and count as asked by the person who made the key or connected the assistant.
For your own code
The same data, as JSON.
A versioned REST API for a data warehouse, an internal dashboard or a script. Lists page with a cursor, and an unknown parameter is an error, never silently ignored.
- /competitors
- Competitors, and one with its pages and focus
- /competitors/{id}/battlecard
- Its battlecard
- /changes
- Changes, newest first, filtered; one with its diff
- /briefs
- Weekly briefs; latest, with the changes it cites
- /products
- Your products' price positions; /products/signals, the moves
curl -H "Authorization: Bearer $ORLEA_API_KEY" \ "https://app.orlea.com/api/v1/changes?category=pricing&since=2026-10-01T00:00:00Z"
{
"data": [
{
"id": "c41f7a2e-5b1d-4e8a-9f30-7d2c6a81b4e9",
"competitor": {
"name": "Brisklane",
"domain": "brisklane.app"
},
"category": "pricing",
"priority": "high",
"headline": "Brisklane cuts Pro to $39 and moves SSO into it",
"facts": [
"Pro: $49 → $39 a month",
"SSO (SAML): Business → Pro"
],
"interpretation": {
"label": "interpretation",
"whyItMatters": "Undercuts your mid-market plan by $10.",
"whatToDo": [
"Refresh the Brisklane battlecard"
]
},
"when": {
"kind": "exact",
"at": "2026-10-14T06:12:09Z"
},
"evidence": [
{
"kind": "page",
"url": "https://brisklane.app/pricing",
"label": "Pricing page"
},
{
"kind": "after",
"url": "https://app.orlea.com/…",
"label": "Copy after"
}
],
"appUrl": "https://app.orlea.com/app/changes/c41f7a2e-…"
}
],
"nextCursor": "eyJ0IjoiMjAyNi0xMC0yMiJ9"
}Shortened: a change also carries its source, summary, tags, triage state and when Orlea recorded it.
Illustration with fictional companies and people.
In detail
What you get.
Competitors
Each one you track, with its pages, when they were last read and what it changes most.
Changes, facts apart from interpretation
What was detected, and Orlea's labelled reading of it, never mixed. Dates as precise as they are known, with the evidence to check.
Briefs and battlecards
Weekly briefs with the changes they cite, and each competitor's battlecard as last written.
Product prices
Your products' price positions and competitors' price moves, on Pro, Team and Enterprise.
Security and limits
Read-only, one workspace, yours to revoke.
The API and MCP server come with Pro, Team and Enterprise. A key carries no more than its maker could read in the app, and you can stop it at any moment.
What a key can do
- Read only
- Every endpoint and every tool reads. Nothing can be created, changed or deleted through a key.
- One workspace
- A key opens the workspace it was made in and nothing else. An id from any other workspace answers as if it didn't exist.
- Shown once, stored as a fingerprint
- A random 32-byte key, shown once when it is made. Orlea keeps its SHA-256 hash, never the key.
- Revocable, and can expire
- Revoke a key in Settings → API and it stops at once. It can expire after 30 days, 90 days or a year, or run until revoked.
- Tied to an admin
- Only owners and admins make keys, and a key works only while its maker is still one. Remove or demote them and their keys stop.
- Keys only, no browser access
- The API never reads a signed-in browser session, and other websites can't call it from a visitor's browser.
Limits
- Rate limits
- 120 requests a minute per key and 300 per workspace. Past that, the answer says when to retry.
- Keys per workspace
- Up to 25 at a time: one per tool or assistant, so each can be revoked alone.
- Usage you can see
- Settings → API shows each key's maker, when it was last used and its requests over 30 days, through MCP and in all.
- Connected apps
- Assistants that sign in read as the person who connected them, in the one workspace they picked, until an admin disconnects them in Settings → API. Not yet: write access, and managing webhooks through the API.
Plans
- Starter, €49 a month
- Not included.
- Pro, €129 a month
- API and MCP server included.
- Team, €349 a month
- API and MCP server included.
- Enterprise
- API and MCP server included.
- Free trial
- Included, so you can connect an assistant before you choose a plan.
How we protect your workspace overall: Security. Prices and every plan's limits: Pricing.
Related
Works well with
FAQ
Questions, answered
Does it work with ChatGPT?
Yes, where ChatGPT offers custom connectors (developer mode; it depends on the ChatGPT plan). Add Orlea's server address, sign in to Orlea and pick the workspace: ChatGPT then reads it as you, read-only. Claude connects the same way; Claude Code, Cursor and VS Code can also use an API key.
Can an assistant change anything in Orlea?
No. Every endpoint and every tool only reads. Triage, rules and settings stay in the app, and there is no write access through the API.
Which plans include it?
Pro, Team and Enterprise, and the free trial. It isn't on Starter. Client workspaces under an agency plan don't offer it yet. A workspace that moves to a plan without it keeps its keys, refused until the plan has it again.
Do questions an assistant asks Orlea count as mine?
They count as asked by the key's maker, or by the person who connected the assistant: toward their 30 questions an hour, and in their recent questions, marked "Via API".
Where is the documentation?
In the app, under Settings → API: every endpoint and tool, and the setup for each assistant. The OpenAPI 3.1 description is public at /api/v1/openapi.json, for Postman, Insomnia or a client generator.
Be the first to know. Every time.
Pick your first competitors in a few clicks and see their last 90 days within minutes.