Connect agents through governed routes.

01 | MCP client

Use Immaculate as the tool admission server

Configure your MCP client to call the Immaculate admission tool before mutating work. The tool returns allow or ask and records the request for later review.

{
  "mcpServers": {
    "immaculate-governance": {
      "command": "node",
      "args": ["<immaculate-root>/scripts/agent-governance/mcp-server.mjs"]
    }
  }
}

02 | API headers

Keep product, evidence, and model keys separate

Use one key lane for tenant product APIs, one for Immaculate and LaaS evidence, and one for Q model access. This lets teams rotate or revoke one lane without breaking every customer workflow.

curl https://aura-genesis.org/api/v1/laas/health \
  -H "Authorization: Bearer <immaculate-key>"

curl https://aura-genesis.org/api/v1/route/evaluate \
  -H "Authorization: Bearer <immaculate-key>" \
  -H "Content-Type: application/json" \
  --data '{"intent":"summarize","surface":"operator"}'

03 | Route contract

Public endpoints developers should know

The production Arobi API surface lives on Aura. iorch links to those docs and keeps the Immaculate MCP/API, JAWS download, status, and checkout pages crawlable.

• GET /api/v1/laas
• GET /api/v1/laas/health
• POST /api/v1/laas/seal
• POST /api/v1/verifier/verify
• POST /api/v1/immaculate/govern
• POST /api/v1/route/evaluate

04 | Deployment rule

Check the live pattern before editing source

Before a deploy, verify the Netlify site id, domain, published deploy, output directory, function bundle, and source root. Then deploy through the guarded script for that site.

• iorch.net: Immaculate dashboard deploy lane.
• aura-genesis.org: Aura guarded deploy lane.
• qline.site: current Qline and JAWS customer source lane only.