Build with Edge Delta
A REST API with a published OpenAPI spec, a hosted MCP server for AI agents, and a CLI. Everything in the platform is automatable.
Developer resources
Programmatic access to pipelines, telemetry, monitors, and AI Teammates, whether you are writing scripts, wiring up agents, or integrating Edge Delta into your own tooling.
API Reference
REST API for pipelines, monitors, dashboards, rehydrations, and AI Teammates at api.edgedelta.com. Authenticate with an API token and automate everything you can do in the app.
MCP Server
A hosted Model Context Protocol server over streamable HTTP. Connect Claude, Cursor, VS Code, or any MCP-capable agent to query logs, metrics, patterns, and anomalies in your organization.
edx CLI
The official command line interface for Edge Delta. Manage pipelines, search logs and metrics, and work with AI Teammates from your terminal or from scripts.
Open Source
The Edge Delta agent ecosystem, exporters, and integrations are developed in the open. Browse the repositories, file issues, and contribute.
Get started in a terminal
Call the API
curl https://api.edgedelta.com/v1/orgs/$ORG_ID/pipelines \ -H "X-ED-API-Token: $ED_API_TOKEN"
Add the MCP server to Claude Code
claude mcp add --transport http edgedelta \ "https://api.edgedelta.com/v1/orgs/$ORG_ID/mcp?token=$ED_API_TOKEN"
Install the CLI
brew install edgedelta/tap/edx # or go install github.com/edgedelta/edx@latest
Agents can discover everything on this page automatically: the OpenAPI spec lives at /openapi.json, the API catalog at /.well-known/api-catalog, the MCP manifest at /.well-known/mcp, and a machine-readable site guide at /llms.txt.
API versioning and deprecation
The Edge Delta REST API is URL-versioned. The current stable version isv1, and every endpoint lives under a versioned path such as/v1/orgs/{org_id}/pipelines. Breaking changes ship as a new URL version rather than as changes to an existing one.
Deprecation policy: when an endpoint or version is scheduled for removal, it is announced in thedocumentationwith a retirement date well in advance, and the replacement is documented alongside it, giving integrations and agents time to migrate before removal.
Requests are subject to standard rate limits to keep the platform healthy. Clients and agents should treat HTTP 429 responses as a signal to back off and retry with delay.