Skip to content
AGENTIC Data Mining
Public-record data · MCP native 15 datasets live now

The public record,
queryable by your agent.

36 datasets — building permits, SEC filings, federal awards, court dockets, sale-barn auctions, FDA enforcement — served through one MCP server as structured JSON. Your agent asks; we return records. One flat subscription; query as much as the strategy needs.

All systems operational
PERMIT #BP-2026-04471 · MARICOPA COUNTY, AZ  ···  SEC FORM 4 · CIK 0000320193  ···  SAM.GOV AWARD · FA8750-26-C-0012  ···  AIS MMSI 367001234 · PORT OF LOS ANGELES  ···  PTR · US SENATE · DISCLOSED 2026-07-02  ···  DOCKET 2:26-cv-04118 · C.D. CAL.  ···  LOT 214 · FEEDER STEERS · 612 LBS · $284.50/CWT  ···  APN 217-08-114 · ASSESSED $1,240,300  ···  NPDES AZ0025861 · MODIFICATION  ···  QUEUE POS 2214 · CAISO · 400 MW BESS  ··· 
One round-trip

Question in, records out.

Your agent calls a dataset tool the way it calls any other MCP tool. The response is normalized JSON with source identifiers intact — a permit number, a CIK, a docket — so every record can be traced back to the filing it came from. No meter runs while it works.

Agent sessionmcp.agenticdatamining.ai

> Which counties issued the most data-center permits last quarter?

tool   permits.datacenter

params { "quarter": "2026-Q2", "group_by": "county", "limit": 3 }

← 3 records

  { "county": "Maricopa, AZ", "permits": 14, "disclosed_mw": 610 }

  { "county": "Loudoun, VA",  "permits": 11, "disclosed_mw": 540 }

  { "county": "Douglas, GA",  "permits": 7,  "disclosed_mw": 380 }

plan   Desk · all sectors · no per-query charge

Process

How it works

  1. 01

    Connect MCP

    Add one server block to your agent config. Every dataset becomes a tool your agent can call.

  2. 02

    Ask your agent

    Plain language in. The agent picks the right tool — permits, filings, dockets, auctions.

  3. 03

    Get structured records

    Normalized JSON back, with source identifiers intact. No scraping, no parsing, no ETL.

  4. 04

    Subscribe once

    Flat monthly subscription for the endpoint. Tiers scale by sectors, refresh cadence, and record volume — never by call count.

Catalog

Four sectors, 15 datasets

15 live now
Browse the full catalog

sec.filings, contracts.awards, ip.filings, sec.fundamentals, health.trials, fda.warning_letters, health.nih_grants, fda.approvals, gov.opportunities, corp.formations, commerce.peptides, and trade.carriers (12 of 34) are live now; the rest of the catalog rolls out over time. Request a dataset to get early access when it ships.

Request a dataset

Need a dataset that isn’t live yet?

Tell us which records you need. The catalog rolls out by demand — what customers ask for ships first.

Pricing

A faucet, not a meter

Full pricing

MCP access is licensed by flat subscription — no per-query metering, no usage anxiety. Tiers scale by sector coverage, refresh cadence, and record volume, so this month's invoice is the number the CFO saw last month.

Annual terms available on every tier. No charge per tool call, ever.

Operations

Built to pass your review, not just your demo

Runs on Azure

Served from Azure infrastructure with full access logs — and a flat invoice, so there's nothing to reconcile at month end.

Named licensees, clean provenance

Every dataset passes source terms-of-service review before listing, and every license names its holder and acceptable use. Your diligence team will ask; the answer is yes.

Records, not conclusions

We serve filings as filed, with source identifiers on every record. Your models draw the conclusions.

Quickstart

One config block away

Paste this into your agent's MCP configuration, set your key, and all 15 dataset tools are live in the session.

Connection kit: one self-contained HTML file — endpoint, auth, config JSON, and all 15 live tools with example calls. Works offline. Dataco Bids .mcpb: drag-install bundle for Claude Desktop for federal-contractor bidding, covering dla.dibbs, contracts.awards, gov.opportunities, and gov.assistance — prompts for your API key (and an optional FSC preset) on install.

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