Your competitive intelligence, in your tools.

Competitors, signals, pricing changes, battlecards and moves: query it all via the MCP connector. A read-only REST API is available on request for Enterprise.

One call, a dated answer

A real request to the public server, and what came back.

  1. Ask by tool name: pricing changes, moves, battlecards
  2. Each change typed, scored for severity and dated
  3. Provenance on every answer: when it was generated and how fresh the data is
  4. The same data your dashboard and briefing use
POST api.industry-lens.com/mcp/public
tools/call get_pricing_changes
{
  "scope": "public",
  "count": 3,
  "pricing_changes": [
    {
      "competitor": "Weflow",
      "change_type": "tier_added",
      "severity": "high",
      "summary": "Weflow — Agent Builder Free tier added at $0",
      "detected_at": "2026-10-04T20:29:32Z"
    },
    {
      "competitor": "Parano.ai",
      "change_type": "price_decrease",
      "severity": "medium",
      "summary": "Parano.ai — Starter price decreased from $89/mo to $79/mo (11%)",
      "detected_at": "2026-09-28T04:31:09Z"
    },
    {
      "competitor": "Parano.ai",
      "change_type": "price_decrease",
      "severity": "medium",
      "summary": "Parano.ai — Pro price decreased from $299/mo to $269/mo (10%)",
      "detected_at": "2026-09-28T04:31:09Z"
    }
  ],
  "provenance": {
    "provider": "IndustryLens",
    "tool": "get_pricing_changes",
    "generated_at": "2026-10-22T19:06:08.660Z",
    "data_as_of": "2026-10-04"
  }
}
Live response, 22 Oct 2026, 19:06 UTC. Some fields trimmed for length.

REST API endpoints: set up on request for Enterprise

GET/v1/competitorsName, domain, market.
GET/v1/signalsScored insights, newest first.
GET/v1/pricing-changesPricing moves, dated.
GET/v1/battlecardsThe current battlecard.
GET/v1/movesA dated moves feed.

These resources ship as a read-only REST API on request for Enterprise. Today, query the same data from Claude, ChatGPT or any MCP-aware tool via the MCP connector, read the developer reference, see the setup guides for Claude and Cursor, or read what a competitive intelligence MCP server does.

Questions about the API.

What plan do I need?

The MCP connector is included on every paid plan, with per-customer keys. A read-only REST API is available on request for Enterprise.

How do I authenticate?

The MCP connector uses a per-customer key issued from account settings. A REST API set up on request uses a bearer API key the same way.

Is the API read-only?

Yes. To write human-reviewed intel back from inside an AI assistant, use the MCP connector’s suggest_intel tool instead.

See the MCP connector →
How is this different from the MCP connector?

Same data, different consumer: the MCP connector is for AI agents mid-task today (Claude, ChatGPT and other MCP clients) and is self-serve on every paid plan. The REST API is for your own code on a schedule you control: it exists, but it isn’t self-serve, we set it up for you on request for Enterprise.

Wire your competitive intelligence into your stack.