ErrorDX Documentation

You need

An ErrorDX account and an organization — app.errordx.com.
A project, which is where its DSN comes from.
A Sentry-compatible SDK for your platform. The guides here cover JavaScript, Node.js and Python; any other Sentry SDK works the same way.
Outbound HTTPS to api.errordx.com from wherever your app runs.

sentry-cli (or @sentry/vite-plugin) for source maps and release artifacts — the upload endpoints are Sentry-compatible. Point the tooling at the API base URL, not the dashboard:
```
# sentry-cli
export SENTRY_URL=https://api.errordx.com
export SENTRY_AUTH_TOKEN=edx_…        # create one in Settings → API tokens
npx @sentry/cli sourcemaps upload ./dist --org <org> --project <project>
```
For bundler plugins (@sentry/vite-plugin and friends), set the same two environment variables in CI. Keep release options off (release: { create: false }) — uploads match events by debug id, which the plugin injects automatically.
The errordx CLI or the MCP server to query issues and traces from a terminal or from an agent. Agents on the MCP server can also mint edx_… tokens directly (create_api_token). See Agents & CLI.

A server, database, queue or object store: ingestion, storage, symbolication and retention all run in the hosted service.
A staging deployment of ErrorDX to test against — create a second project instead, so test traffic never lands in the same issue stream as production.