One config block away

Quickstart

Paste this into your agent's MCP configuration and set your key. On connection, the server advertises every dataset tool your subscription carries.

{
  "mcpServers": {
    "agentic-data-mining": {
      "url": "https://mcp.agenticdatamining.ai/api/mcp",
      "headers": {
        "X-Api-Key": "${ADM_API_KEY}"
      }
    }
  }
}

1. Sign up, pick a tier, and copy your sector keys from the account console.
2. Export it as ADM_API_KEY in your agent's environment.
3. Restart the session. Ask a question; the agent picks the tool.

https://mcp.agenticdatamining.ai/api/mcp/k/{admc_token}

# mint
curl -sS -X POST https://mcp.agenticdatamining.ai/api/mcp/tokens \
  -H "X-Api-Key: adm_live_…"

# revoke
curl -sS -X POST https://mcp.agenticdatamining.ai/api/mcp/tokens/{id}/revoke \
  -H "X-Api-Key: adm_live_…"

Authentication

Every request carries an API key. Each sector of data has its own key — a leaked key never exposes more than one sector, and you can rotate any one from the account console without touching the others; old keys expire after a 24-hour grace window. Developer accounts hold keys for the two sectors chosen at signup; Desk and Institutional hold all seven.

X-Api-Key: adm_live_9f27c1…

Keys never appear in query strings, and we log key ID — not key material — in access logs.

Shared parameters

Every dataset tool accepts these; each tool adds dataset-specific filters, served in the tool's input schema at connection time.

Tool reference

15 tools, one per live dataset. Full schemas, coverage notes, and sample records are on each dataset page in the catalog. More ship through 2026 — request a dataset to prioritize one.

Errors

Errors come back as structured tool results, so agents can recover without human help. There is no rate-limit error tied to billing — flat means flat. If a tool is failing repeatedly, check the service status page before writing in.