ABN Developer API — early access

Early access — in development

The ABN developer API is in active development and available to early-access partners. It is not generally available yet — the surfaces below describe the intended integration and security model, the shapes may change, and the endpoints are not callable from this page today. Request early access and we will involve you as it ships.

Request early access →

01 — Integration model

How you will integrate

REST for polling and controlled actions

Read agent metadata and results, trigger a governed run, or simulate one with no writes — on a cadence you control.

Webhooks for event delivery

ABN pushes events (run completed, critical finding, proposal created) to an endpoint you register. Each delivery is HMAC-signed.

Dry-run simulation for no-write testing

Preview what an agent would do before anything is proposed — the same simulation the platform uses internally.

Attestation verification

Every signed finding can be verified back to the source records it was computed from (the Result Attestation Layer).

02 — Security model

Scoped, governed, signed

Scoped API keys

Tenant-bound access

Role-based permissions

HMAC-signed webhooks

Human-approval states exposed in API responses

No hidden writes

03 — Planned API surface

The shape we are building (not callable today)

The endpoints below describe the intended API surface for early-access partners. They are not generally available and the paths and schemas may change before launch.

Planned base URL

https://api.abnplatform.com/v1

Planned auth

Authorization: Bearer <scoped key>

GET/v1/agentsList agents
GET/v1/agents/{id}Get agent details
GET/v1/agents/{id}/resultsGet latest results
POST/v1/agents/{id}/runTrigger a governed run
POST/v1/agents/{id}/simulateDry-run simulation (no writes)
GET/v1/agents/{id}/attestationVerify the latest run
GET/v1/connectorsList connected systems
GET/v1/healthSystem health status
POST/v1/webhooksRegister a webhook endpoint

04 — Webhooks

Event delivery (planned)

Never trust a webhook payload until the signature is verified. Treat webhooks as notifications; fetch the authoritative result from the ABN API if the receiving system will trigger a downstream action. Each delivery will carry an X-ABN-Signature header — verify it with HMAC-SHA256 keyed by the webhook's secret before trusting the payload.

Planned event types

agent.run.completed

Fires after a successful run. Carries summary, confidence and an attestation pointer.

agent.finding.critical

Fires when an agent flags a finding above the critical impact threshold in the tenant policy.

agent.proposal.created

Fires when a TIER 2 PROPOSE_CHANGE proposal lands awaiting human approval.

Example payload (illustrative)

POST {your_endpoint}application/json · example

{
  "event": "agent.run.completed",
  "delivered_at": "2026-05-24T09:14:22Z",
  "tenant_id": "tnt_5a3fc0",
  "agent": {
    "id": "agt_invoice_audit_42",
    "name": "Freight invoice auditor",
    "archetype": "ANALYZER"
  },
  "run": {
    "id": "run_2f8b1c",
    "status": "completed",
    "confidence": 0.94,
    "tier": "PROPOSE_CHANGE"
  },
  "summary": {
    "findings_count": 3,
    "primary_recommendation":
      "Review invoice INV-118 against route R-118 — +18.5% deviation."
  },
  "attestation": {
    "id": "att_run_2f8b1c",
    "hmac": "sha256=…"
  }
}

Verifying the signature

/v1

import hmac, hashlib

def verify_abn_signature(body: bytes, header: str, secret: str) -> bool:
    """Validate an ABN webhook signature header."""
    expected = "sha256=" + hmac.new(
        secret.encode(), body, hashlib.sha256
    ).hexdigest()
    return hmac.compare_digest(expected, header)

Get started

Request early access

The developer API rolls out to early-access partners first. Tell us what you want to build and we will involve you as the API ships.

Request early access →See pricing

Build on ABN— the developer API — early access