Connect your workflow.
Run environmental screening from your GIS tools, business systems, or AI agents using REST or the Model Context Protocol (MCP).
Model Context Protocol (MCP) Server
Connect an MCP-compatible client to the Streamable HTTP server. The endpoint and protocol details are below.
Endpoint: https://eia-landing.pranay-442.workers.dev/mcp
Transport: Streamable HTTP (JSON-RPC 2.0)
Protocol Version: 2024-11-05
Available MCP tools
Screen a project’s sector, location, boundaries, and terrain for review risks.
Check required distances to protected habitats, waterways, and settlements.
Estimate financing and project costs associated with a review delay.
Look up supported regions, review authorities, and screening requirements.
Get a sandbox key
Create sandbox credentials with this REST request:
curl -X POST https://eia-landing.pranay-442.workers.dev/api/v1/sandbox/keys \
-H "Content-Type: application/json" \
-d '{"agentName": "EiaAuditAgent", "environment": "sandbox"}' Handle errors
All API endpoints and error responses return structured application/problem+json with machine-readable codes and remediation hints:
{
"type": "https://eia-landing.pranay-442.workers.dev/docs/errors#invalid-coordinates",
"title": "Invalid Spatial Coordinates",
"status": 400,
"detail": "Provided latitude 36.12 and longitude -115.15 fall outside regional planning district boundaries.",
"code": "INVALID_COORDINATES",
"hint": "Verify decimal WGS84 coordinates in project boundary polygon or GeoJSON."
}