Eridian Dev

Eridian Dev is the engineering vertical on the Eridian control plane. Completions, reviews, codebase Q&A, test generation, and pull-request summaries all run as ordinary inference through GPT and Gemini, with the same residency, PII, budget, and audit rules as the rest of the institution.

This page gets a project to first review. Detailed contracts live on the pages linked below.

What you get

Every workflow is a project-scoped API. There is no separate "Dev cluster." POST /v1/dev/* is a typed surface on top of Inference.

Prerequisites

1. A project with vertical dev (example: prj_dev_001).
2. An eridian_sk_ key with inference:write, dev:write, and models:read.
3. A residency pin. Engineering source is Customer Data. See Regions.
4. At least one connected repository. See Repositories.

First review

POST /v1/dev/reviews
Host: api.geteridian.com
Authorization: Bearer eridian_sk_...
Content-Type: application/json
Idempotency-Key: pr-4821-review-v1
X-Eridian-Project: prj_dev_001

{
  "repository_id": "repo_payments_core",
  "pull_request": {
    "host": "github",
    "number": 4821,
    "head_sha": "8f3a2b1c"
  },
  "model": "auto",
  "routing_policy": "quality_optimized"
}

{
  "id": "rev_4821_01",
  "object": "eridian.dev.review",
  "status": "completed",
  "model": "gpt",
  "findings": [
    {
      "path": "src/ledger/posting.ts",
      "line": 214,
      "severity": "high",
      "title": "Unbalanced posting on retry without Idempotency-Key",
      "citation": "src/ledger/posting.ts:198-220"
    }
  ],
  "eridian": {
    "request_id": "axm_req_dev_8f3a",
    "route": "gpt",
    "region": "eu-west-1",
    "cost_usd": 0.086,
    "cache_hit": false
  }
}

Required scope: dev:write. The review is an audit event (dev.review.completed). Raw source is not stored on ZDR projects after the response returns.

Model policy

Use "auto" unless an eval has pinned the workflow.

Do not send provider SKU strings. See Models.

Dashboard

Open Eridian Dev in the workspace. You should see repository index status, review volume, cache hit rate on completion prompts, and cost by desk. Cost attribution uses the same Usage meters as Core API.

Next steps

• Connect a repository
• Pin completion in the editor
• Require reviews in CI
• Read the Dev API
• Check limits

Troubleshooting

Support: contact@geteridian.com. Engineering on-call for the gateway is documented in Runbooks.