REST APIHTTP GET · OpenAPI 3.1·MCP ServerJSON-RPC 2.0 · HTTP POST
Developer API
Access BattleMaps competitive intelligence via REST API or MCP. Same data, same API keys, same billing — pick the integration style that fits your stack.
Your API Keys
One key works for both REST and MCP. Same monthly allotment and credit pool.
Quick start
Try it now
Search companies with a single curl:
curl -H "Authorization: Bearer bm_live_..." \
"https://battlemaps.io/api/v1/companies?query=CRM&limit=5"Base URL
https://battlemaps.io/api/v1Endpoints
GET
/api/v1/companiesGET
/api/v1/companies/:slug/intelGET
/api/v1/markets/:slugGET
/api/v1/intelGET
/api/v1/openapiMachine-readable OpenAPI 3.1 spec at GET /api/v1/openapi — no auth required.
Endpoints
Click an item to see its parameters and an example.
What you can ask
›“Who are the top enterprise CRM vendors by funding stage?”
›“What has Salesforce announced in the past 30 days?”
›“Show me all product-led companies in the data warehousing market.”
›“What funding rounds happened in AI code assistants this week?”
›“Compare HubSpot and Pipedrive across GTM dimensions.”
›“Which companies in the CRM market recently changed leadership?”
REST API vs MCP Server
| REST API | MCP Server | |
|---|---|---|
| Protocol | HTTP GET | JSON-RPC 2.0 POST |
| Best for | Agents, CLIs, scripts, direct HTTP | Claude Desktop, Cursor, MCP-native clients |
| Discovery | GET /api/v1/openapi (OpenAPI 3.1) | tools/list method |
| Keys & billing | Shared pool | Shared pool |
| Latency | Sub-50ms edge | Sub-50ms edge |
Machine-readable docs
OpenAPI 3.1 spec at GET /api/v1/openapi for agent discovery and SDK generation. An llms.txt is also available for AI crawlers.