Integrations
WHAT IS ACTUALLY CONNECTED.
A logo wall is not a certification. This page uses three words and means something specific by each of them, and the status shown for every adapter is the one recorded in the repository — not a roadmap.
| Status | What it means |
|---|---|
| Proven | A real provider request went through Elixir’s loop to a canonical result, and Elixir’s independent verification accepted it. Both certification cases passed: a real defect, and a false incident that had to be refused. |
| Implemented | Implemented and tested against fixtures. No live target was available to prove it against. |
| Certification pending | Implemented, registered and structurally tested. No real provider request has ever been made from this build, because no credential or endpoint for one was available. |
Passing unit tests, HTTP mocks, schema validation and documentation are not proof. The build has no mock mode for the certification evaluation, for exactly that reason.
Executors
MANAGED AGENT RUNTIMES
The provider owns its own loop inside its own sandbox. Both of these have driven real sessions through Elixir to a verified result.
Claude Code
ProvenShell, a named-command allowlist, and the only adapter that reports cost in dollars. Requires the claude CLI, authenticated; an expired session presents as an auth failure rather than a silent fallback.
executor:
adapter: claude-codeCodex
ProvenSandboxes by workspace rather than by named commands, and reports tokens rather than money — so cost_usd is null and the reservation stands as the charge. Requires the codex CLI, authenticated.
executor:
adapter: codexExecutors
MODEL RUNTIME ADAPTERS
Elixir owns the loop and executes every operation itself. A model runtime may never hold a shell — it has no sandbox of its own, so the shell would be unrestricted.
Anthropic API
Certification pendingImplemented, registered and structurally tested. No real provider request has been made.
adapter: anthropic-api
ELIXIR_ANTHROPIC_API_KEY
OpenAI API
Certification pendingImplemented, registered and structurally tested. No real provider request has been made.
adapter: openai-api
ELIXIR_OPENAI_API_KEY
Gemini
Certification pendingImplemented, registered and structurally tested. No real provider request has been made.
adapter: gemini
ELIXIR_GEMINI_API_KEY
OpenAI-compatible / local
Certification pendingFor self-hosted and private inference endpoints. Unproven because no such endpoint was reachable from this build. Tool calling is an operator assertion, not an Elixir claim.
adapter: openai-compatible
ELIXIR_OPENAI_COMPATIBLE_API_KEY
AWS Bedrock
Certification pendingImplemented, registered and structurally tested. No real provider request has been made.
adapter: bedrock
ELIXIR_BEDROCK_API_KEY
Azure OpenAI
Certification pendingImplemented, registered and structurally tested. No real provider request has been made.
adapter: azure-openai
ELIXIR_AZURE_OPENAI_API_KEY
Vertex AI
Certification pendingImplemented, registered and structurally tested. No real provider request has been made.
adapter: vertex-ai
ELIXIR_VERTEX_AI_API_KEY
Enterprise gateway
Certification pendingFor an internal model gateway that fronts one or more providers. Unproven because no such gateway was reachable from this build.
adapter: enterprise-gateway
ELIXIR_ENTERPRISE_GATEWAY_API_KEY
Observation
RUNTIME ADAPTERS
How Elixir sees a fleet. Read-only, always — a runtime adapter has no write path, and observation is a separate system from treatment.
supervisord
ProvenMechanism
supervisorctl status
Live-proven read-only against a real host — 33 supervised programs, 2026-08-29 — while reporting a completely different fleet from the Hermes adapter reading the same machine.
Limit of the proof
One host. Program-to-worker mapping is left to your registry, never guessed.
systemd
ProvenMechanism
systemctl show, for services and timers
Live-verified on a disposable Ubuntu 26.04 LTS systemd-managed VM — systemd 259, PID 1 /usr/lib/systemd/systemd, systemctl is-system-running reporting running, 24 managed services. Five long-running services were observed and each agreed with systemctl show; active/exited oneshots were distinguished from running; a nonexistent unit was reported absent rather than invented; read_only held throughout, over exactly two commands.
Limit of the proof
Proven on one Ubuntu 26.04 / systemd 259 environment, on ordinary system units rather than an agent workforce. Broader distribution and version coverage is still expanding. Observation was proven — not restart, treatment or fleet control, none of which this adapter has.
Hermes profiles
ProvenMechanism
hermes profile list, over ssh, via a shipped read-only probe
Live, against 16 workers of recorded output held as evidence in the repository.
Limit of the proof
One fleet kind, reached over ssh by a probe that ships with the tool.
Interfaces
HOW INCIDENTS REACH ELIXIR
Public API
ShippedA bearer-authenticated HTTP interface for reporting an incident and reading back the incident, the result and the evidence.
POST /v1/incidents
GET /v1/incidents/inc_…
GET /v1/incidents/inc_…/result
GET /v1/incidents/inc_…/evidence
GET /v1/agentsThe API holds no treatment authority. An API key can report and read; no key can be issued a scope that approves anything.
MCP
ShippedSix tools over stdio, so a compatible AI client can report its own incident and read the verified outcome.
- elixir_list_agents
- elixir_get_agent
- elixir_report_incident
- elixir_get_incident
- elixir_get_result
- elixir_get_evidence
MCP imports nothing internal and does not know the words billing or entitlement. It can report incidents. It cannot approve its own treatment.
Not yet
WHAT IS NOT HERE
Kubernetes
There is no Kubernetes runtime adapter. Three adapters exist: supervisord, Hermes profiles and systemd.
A hosted service
Elixir is self-hosted. There is no SaaS control plane and no managed offering.
Hosted agent operations
Elixir remains self-hosted. AgentDoctorMD hosts only checkout activation and subscription entitlement synchronization; it cannot reach an executor, agent or customer VM.
SSO and RBAC
Named on the Enterprise plan as a discussion, not shipped. Organization isolation exists; SSO does not.
An npm package
Elixir is not published to npm. It is distributed as a certified release artifact, downloadable and checksum-verifiable from its release page.