# API and data access

Understand the transport behind the dashboard, CLI, and MCP.


## Authentication paths

CLI and MCP use authenticated API requests. They do not replace the collector or database. Public ingestion keys accept project telemetry; platform credentials authorize management/read operations. Keep these credential types separate.

## Common read paths

| Route | Purpose |
| --- | --- |
| `GET /v1/projects` | Accessible projects |
| `GET /v1/projects/:id/components` | Project applications and repository context |
| `GET /v1/projects/:id/incidents` | Grouped problems |
| `GET /v1/projects/:id/incidents/:incidentId/evidence` | Incident evidence |
| `GET /v1/projects/:id/services` | Services and monitor state |
| `GET /v1/projects/:id/events` | Event summaries and available environment/release context |
| `GET /v1/projects/:id/usage` | Account telemetry counters and limits |
| `GET /v1/projects/:id/events/:eventId/original` | Accepted event archive data |

Project access checks still apply. Some operations require ownership; knowing a UUID or installation ID does not grant access.

## Ingestion and builds

SDKs POST telemetry to `/ingest`; replay uses `/ingest/replay` and finalization. Build reporters use `/release` and source-map uploads use `/sourcemaps`. Prefer the SDK/build tools so batching, keys, filtering, and retries follow their contracts.

## MCP is the agent interface

Use the named MCP tools when working through a coding agent instead of inventing private HTTP calls. `get_incident_context` aggregates several evidence routes and records active investigation state. Tool descriptions and account permissions are part of that workflow.

See [MCP](/docs/agents/mcp), [keys](/docs/reference/keys), and [usage](/docs/platform/usage).