The shape of it
One REST endpoint per tool. Authenticate with your site key, send JSON, get JSON — the same data the app renders, with no scraping and no HTML parsing.
POST https://ranker.monster/api/v1/keywords/research
Authorization: Bearer <your-site-key>
Content-Type: application/json
{
"project_id": 12,
"seed": "shipping boxes",
"location": "CA",
"language": "en",
"limit": 100
}Endpoints
| Endpoint | What it returns |
|---|---|
/projects | Create, list and archive projects. |
/keywords/research | Keyword ideas around a seed, with volume, difficulty, cost per click and intent. |
/keywords/overview | One keyword: trend, difficulty, intent, and the current results page. |
/tracking/configs | Tracking configurations: domain, market, devices, schedule. |
/tracking/run | Trigger a run, or estimate what one costs first. |
/tracking/results | Latest positions, or history for a keyword. |
/domain/overview | Authority, organic keywords, traffic and competitors for any domain. |
/domain/organic | The full ranked-keyword table, filterable. |
/backlinks/summary | Referring domains, totals, and the gained/lost trend. |
/backlinks/rows | Individual links with anchors and first-seen dates. |
Keys and limits
Keys are issued per project from your account. A key can be read-only or allowed to trigger runs, and every call is metered against your plan — the response tells you what it cost.
Claude
The same endpoints are exposed to Claude, so an agent can research keywords, read rankings and pull a backlink profile without a browser. Nothing extra to install; the key is the permission.