Integrations
AGLedger fits underneath the platforms you already run. Your observability stack stays. Your SIEM stays. Your webhook consumers stay. AGLedger records sit alongside them, and carry the join keys and event streams that let everything line up.
OpenTelemetry · Langfuse · Arize · Datadog · Honeycomb · OCSF · CloudEvents
Last updated: 2026-05-25 · API v0.25.4
Trace correlation
Carry the trace ID inside the signed envelope
AGLedger does not ingest your traces, proxy your calls, or replace your observability platform. The agent supplies the trace identifier it already has — from OpenTelemetry, Langfuse, Arize, Datadog, Honeycomb, or any of the trace tools listed below — and AGLedger stores it inside the signed record under metadata.traces.
The hash of the record's payload — including the trace block — is what gets signed. If anyone later disputes which trace was referenced at the moment the work was notarized, the signed chain settles the question. The record points at the trace; the trace lives where it has always lived.
| Key | System | Format |
|---|---|---|
otel_trace_id / otel_span_id | OpenTelemetry / W3C TraceContext | 32 hex / 16 hex |
langsmith_run_id | LangChain LangSmith | UUID |
langfuse_trace_id | Langfuse | string |
helicone_request_id | Helicone | UUID |
arize_trace_id / phoenix_span_id | Arize / Arize Phoenix | string / hex |
braintrust_span_id | Braintrust | string |
traceloop_trace_id | Traceloop / OpenLLMetry | string |
langgraph_run_id | LangGraph | UUID |
datadog_trace_id | Datadog APM | uint64-as-string |
honeycomb_trace_id | Honeycomb | hex |
mlflow_run_id | MLflow | UUID |
wandb_run_id | Weights & Biases | string |
Use the keys that apply. Unknown keys are accepted but not part of the convention — stick to this set so downstream consumers can rely on the shape. Full reference in the framework-neutral integration guide.
Webhooks
Record events delivered to your existing systems
AGLedger emits an event at every business-meaningful moment in the record lifecycle — created, completion submitted, fulfilled, failed, delegated, disputed, settled — as an HTTPS POST to an endpoint you register. Every delivery is signed: HMAC-SHA256 for systems only you consume, and Ed25519 RFC 9421 for Settlement Signals a counterparty has to trust. Delivery is at-least-once with stable idempotency keys, a circuit breaker, retry, and a dead-letter queue you can replay. Payloads ship in AGLedger's native envelope or CloudEvents 1.0.
The event surface, both signing schemes, and the delivery guarantees are covered on the webhooks capability page; the webhook guide has the consume-and-verify code.
SIEM export
OCSF events into your security operations pipeline
AGLedger emits Open Cybersecurity Schema Framework (OCSF) events for every state transition, completion submission, verdict, settlement signal, and dispute action. Two push channels ship out of the box: file (newline-delimited JSON for log shippers) and HTTP (POST to a collector endpoint with configurable auth).
The OCSF taxonomy maps cleanly onto Splunk, Microsoft Sentinel, Datadog Cloud SIEM, Sumo Logic, Chronicle, and any SIEM that consumes the schema. Alert rules, dashboards, and correlations written against OCSF work against AGLedger events without translation.
Webhooks carry events as they happen; SIEM export carries the same events in a security-team-native shape. Subscribe to both, or use whichever fits your operating model.
API surfaces
REST, plus SDKs, CLI, and MCP server
Anything that speaks HTTP can call AGLedger directly. The TypeScript SDK, Python SDK, CLI, and MCP server are thin wrappers over the same REST surface, included where they reduce friction.
nextSteps, suggestion, and hint fields where useful, so agents learn the surface in-band. Errors follow RFC 9457 Problem Details with directive guidance, not just diagnostics.npm install @agledger/sdk — thin typed wrapper, no opinion on framework.pip install agledger — matching surface to the TS SDK, same shape.npm install -g @agledger/cli — scriptable from any shell or CI pipeline.npm install -g @agledger/mcp-server — for agent hosts that prefer MCP tool discovery. Same record lifecycle, exposed as MCP tools.Full API reference in the API reference. SDKs and CLI in the SDK guide.
Related capabilities
The underlying HTTP surface every integration calls — lifecycle, webhooks, federation, and SCITT endpoints.
Lifecycle transitions in Verify mode are what fire most webhooks — proposal, acceptance, completion, verdict.
Cross-org event projection — how a remote Server's verdict surfaces as a local webhook event.
Webhook signing (HMAC and Ed25519), SSRF protection on delivery URLs, and the rotation model for integration credentials.
How agents discover our API without scaffolding and why the discovery surface itself is an integration primitive.
Integration patterns for wiring AGLedger into existing agent-governance and observability stacks.