API · Connectors · Integrity
CounterAudit ingests events from your stack, normalizes them to a canonical audit packet, and prepares them for sealing, chain linking, and external timestamp anchoring—so security and compliance get one coherent trail across frameworks and clouds.
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.
Authenticate with API keys in the same family as your other production systems (format and rotation patterns documented with the full API release).
POST /v1/audit/ingest Content-Type: application/json { "connector_id": "langchain-v0.3", "raw_event": { "event": "chain_end", "run_id": "…" }, "org_id": "550e8400-e29b-41d4-a716-446655440000" }
First-party connectors preserve full packet fidelity for trust and provenance platforms already in your architecture.
Language-native callbacks and wrappers meet agents where they run—without forcing every team through the same middleware.
Map cloud control-plane and observability events into the same canonical schema with field-mapping configuration.
@counteraudit/sdk (TypeScript) and counteraudit (Python) will mirror the product specification—callbacks for common orchestration stacks and offline chain verification helpers for CI and security gates.
Prompt and sensitive payloads are hashed—not persisted in audit records. Keys are referenced by id (KMS-ready). Timestamping is designed to run asynchronously so ingest stays resilient when a TSA is unreachable.