Developers

Integrate Aegis Arbiter in minutes.

Create runs, retrieve evidence, approve when required, and kill when necessary. Local-first by default.

Aegis Arbiter overview Request access Back to home

Run the service

# From the Aegis Arbiter (Revenant Core) repo
python -m revenant_core --state-dir .\state --port 8080 --mode safe

# Health check
curl -s http://127.0.0.1:8080/health

Create and inspect a run

# Create a run
curl -s -X POST http://127.0.0.1:8080/runs \
  -H "Content-Type: application/json" \
  -d '{"mode":"plan_only"}'

# Status + evidence
curl -s http://127.0.0.1:8080/runs/<run_id>
curl -s http://127.0.0.1:8080/runs/<run_id>/evidence

Approvals and kill switches

# Approve a pending approval record
curl -s -X POST http://127.0.0.1:8080/runs/<run_id>/approve \
  -H "Content-Type: application/json" \
  -d '{"approval_id":"<id>"}'

# Deny
curl -s -X POST http://127.0.0.1:8080/runs/<run_id>/deny \
  -H "Content-Type: application/json" \
  -d '{"approval_id":"<id>"}'

# Kill a run / kill all
curl -s -X POST http://127.0.0.1:8080/runs/<run_id>/kill
curl -s -X POST http://127.0.0.1:8080/kill-all

Aegis Arbiter is designed to fail closed. If something is uncertain, capability tightens rather than expands.

Need help integrating?

Email hello@protocolops.com with your use case and environment details.