Agentic Infrastructure

Model Context Protocol (MCP) & Developer APIs

Integrate automated statutory environmental audits directly into your enterprise ERP, GIS mapping software, or autonomous reasoning agents via Streamable HTTP MCP and OpenAPI 3.1.0.

Model Context Protocol (MCP) Server

Erayaha provides a native, streamable HTTP MCP server running on Cloudflare Workers edge. Connect Claude Desktop, Cursor, Antigravity, or custom agent frameworks to evaluate environmental proposals in real time.


Endpoint: https://eia-landing.pranay-442.workers.dev/mcp

Transport: Streamable HTTP (JSON-RPC 2.0)

Protocol Version: 2024-11-05

Exposed MCP Tools

eiaAuditPreSubmission Read-Only

Evaluates project category, statutory jurisdiction, spatial boundary parameters, and terrain characteristics to return a comprehensive pre-submission risk audit and screening analysis.

eiaCheckStatutorySetbacks Read-Only

Verifies spatial distance buffers to protected habitats, sensitive ecological areas, wetlands/waterways, and declared human settlements under applicable statutory frameworks.

eiaCalculateProponentDelayRoi Read-Only

Computes the financial carrying costs and capital loss risks associated with regulatory inquiry delays and deficiency cycles.

eiaGetJurisdictionMatrix Read-Only

Retrieves statutory review thresholds, lead agency mandates, and pre-submission screening requirements across supported international jurisdictions.

Instant Self-Serve Sandbox Keys

AI agents can provision sandbox credentials instantaneously via a single REST call without human approval:

curl -X POST https://eia-landing.pranay-442.workers.dev/api/v1/sandbox/keys \
  -H "Content-Type: application/json" \
  -d '{"agentName": "EiaAuditAgent", "environment": "sandbox"}'

RFC 9457 Typed Error Models

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."
}