Skip to content
All engineering use cases

Environmental due diligence data APIs

Combine regulated activity, ground conditions and ecological constraints with commercial search options. Compare listed sources, access requirements and evidence for environmental due diligence data apis.

5 sources · For engineering consultants. Enrichment describes potential applications; review source evidence and limitations.

Public registers are not a complete contaminated-land liability assessment; commercial reports carry their own terms.

Discover sources with MCP

Add this server to an HTTP-compatible MCP client, then call get_source to inspect the first source. The tool call is shown separately from the client configuration. Review upstream access details before requesting data.

{
  "mcpServers": {
    "terramcp": {
      "url": "https://terramcp.earth/mcp"
    }
  }
}

// After connecting, call this discovery tool:
{
  "name": "get_source",
  "arguments": {
    "slug": "ea-public-registers"
  }
}

Listed sources

Frequently asked questions

Which listed sources support Environmental due diligence data APIs?

Start with EA Public Registers, BGS Geoindex, MAGIC. Combine regulated activity, ground conditions and ecological constraints with commercial search options.

What should I check before using these sources for environmental due diligence data apis?

Public registers are not a complete contaminated-land liability assessment; commercial reports carry their own terms.

How do I inspect EA Public Registers through MCP?

Connect an MCP client to https://terramcp.earth/mcp and call get_source with slug ea-public-registers. Review its provenance, access requirements and limitations before contacting the upstream service. Discovery does not make every listed source directly executable through the router.

Are these sources free and independently verified?

Access and licence terms belong to each upstream provider; some products require registration or payment. Open each listing for evidence, health status and enrichment provenance. A wrapper and its underlying API can refer to the same dataset and are not independent observations.