CounterAudit · API · Connectors · Evidence

Instrument agents. Ship evidence the regulator accepts.

CounterAudit is the developer platform for governance evidence. Ingest events from your stack, normalize them into canonical packets, and seal them into tamper-evident records for audit, security, and compliance workflows.

Admissible evidence in, not forensic cleanup later.

POST /v1/audit/ingest GET /v1/audit/verify/:packet_id GET /health → ok 7 built-in connectors shipping MCP tools + proof descriptors

quickstart · curl

curl -X POST https://api.counteraudit.io/v1/audit/ingest \
  -H "Authorization: Bearer <api_key>" \
  -H "Content-Type: application/json" \
  -d '{"connector_id":"openai-assistants-v2","org_id":"<org_id>","raw_event":{"event":"run_completed","run_id":"run-001"}}'

CounterAudit developer API post template showing evidence API output.

See integration flow OpenAPI spec API status Enterprise site Pricing

REST ingest for regulator-ready receipts

Send a connector identifier, organization context, and the raw event payload. The service hashes the raw event, applies connector mapping, and returns packet identifiers for verification workflows as the pipeline is fully deployed.

Example request

Authenticate with API keys in the same family as your other production systems (format and rotation patterns documented with the full API release).

HTTP · application/json

POST /v1/audit/ingest
Content-Type: application/json

{
  "connector_id": "openai-assistants-v2",
  "raw_event": { "event": "run_completed", "run_id": "…" },
  "org_id": "550e8400-e29b-41d4-a716-446655440000"
}

Built-in connectors shipping in production: countersig-native, provenanceai-native, langchain-v0.3, autogen-v0.4, openai-assistants-v2, aws-bedrock, and azure-ai-foundry.

Native connectors

Built-in maps for Countersig-native and ProvenanceAI-native events, plus LangChain, AutoGen, OpenAI Assistants, AWS Bedrock, and Azure AI Foundry.

Custom registry

Register your own connector identifiers and map raw events into the canonical CounterAudit evidence model through the registry API.

Proof endpoints

Ingest, verify, chain-verify, and export through REST, SDKs, or MCP tools with the same schema across environments.

Production connectors

CounterAudit ingests audit trails from native suite connectors and major agent stacks. Pair with CounterAegis when you need identity and provenance layers in the same incident timeline.

countersig-native provenanceai-native langchain-v0.3 autogen-v0.4 openai-assistants-v2 aws-bedrock azure-ai-foundry

SDKs available now

@counteraudit/sdk v0.1.0 (TypeScript/Node.js) and counteraudit v0.1.0 (Python) are published and production-ready—full REST client, callbacks for orchestration frameworks, and offline chain verification for CI pipelines and security gates.

npm install @counteraudit/sdk pip install counteraudit OpenAPI 3.0 spec

MCP tooling for agent pipelines

CounterAudit ships MCP proof tools and descriptors so agent runtimes can record, verify, and export evidence with the same schema as REST and SDK flows. MCP smoke tests are wired in CI to keep tool contracts production-safe.

proof_record proof_verify proof_chain_verify proof_export

Enterprise hardening shipped

Recent platform updates close operational gaps for production deployments: scheduled policy-loop triggers, fail-closed verification behavior, Redis-backed idempotency guarantees, and chain-integrity validation across seal-key rotation.

Scheduled debt-loop worker Manual restore enforcement Redis-required idempotency in prod Chain-valid-after-rotation tests

Enterprise-grade operations

Proprietary technology built for production: prompt and sensitive payloads are hashed—not persisted. Keys are KMS-ready. Timestamping runs asynchronously so ingest stays resilient. Automated health monitoring, daily backups, and documented disaster recovery procedures included. Available as managed SaaS or on-premise deployment.

Uptime monitoring Automated backups SOC 2 ready