HTTPExporter, the agentegrity pro command and the TypeScript client. Any backend that implements the exporter HTTP API receives the same requests.
For the console itself, see the Agentegrity Pro section: create an ingest token, connect an agent to a workspace, and what each screen shows, starting from the overview.
Turn on streaming with environment variables
Set two variables in the agent’s environment and every Python adapter attaches anHTTPExporter when it is constructed. Your code does not change.
Both a token and a URL must be present. With either missing, nothing is attached and the adapter stays local. Attachment is never silent: the adapter logs
agentegrity: streaming session data to <origin> at INFO on the agentegrity.adapters logger, and the session summary lists the sink under exporters (see Checking which sinks are attached). Neither shows the token.
The coding-agent hook runtime builds its adapters the same way, so setting these variables where Claude Code or Codex runs streams those sessions too. When the hook falls back to in-process evaluation (no Unix sockets, or a runtime directory that is not private), it does not stream.
Attach it in code
HTTPExporter is importable from agentegrity and agentegrity.exporters.
str
required
Backend origin. A trailing slash is removed.
str
required
Ingest token, sent as a Bearer credential on every request.
float
default:"5.0"
Per-request timeout in seconds. Keyword-only.
AGENTEGRITY_TOKEN and a URL are also set, the adapter attaches its own instance as well, and the backend receives every request twice.
How delivery works
The exporter never sends from the agent’s thread. Each callback puts a request on a FIFO queue, and one background daemon thread per exporter POSTs them in order with the standard library’surllib.
Ordering. The adapter schedules exporter callbacks without awaiting them, so on_session_start and the first on_event can complete in either order. The ingest API rejects an event for a session it has not seen (404), so a single ordered worker is what guarantees the session exists before its events arrive.
Queue limit. The queue holds 1,000 requests. When it is full, new requests are dropped and each drop logs a warning with a running count (agentegrity exporter: queue full, dropped ...). Nothing retries a dropped or failed request.
Fail-open. HTTP errors, timeouts and connection failures are logged as warnings and the request is discarded. The agent never sees them.
Process exit. When the worker starts, the exporter registers an atexit handler that waits up to 5 seconds for the queue to drain. You can call flush(timeout=5.0) yourself; after a flush, the exporter stops accepting new requests.
Framework label. If the profile’s framework field is empty, on_session_start fills it with the adapter name (for example langchain) in the copy it sends, so the backend can group agents by framework. Your profile object is not modified.
Transport. The URL must be HTTPS, or a loopback host (localhost, *.localhost, 127.0.0.1, ::1). HTTPExporter raises ValueError for any other URL, and with the environment variables the adapter attaches nothing and logs a warning instead, because events carry prompts and tool output as well as the token. Redirects are not followed: a 3xx answer is logged as an error, since urllib would otherwise send the Authorization header to the redirect target.
The agentegrity pro command
agentegrity pro checks a token against a backend and can then run your agent with streaming turned on.
The command first sends
GET <url>/ingest/verify with the token and prints connected to <url> (workspace: <name>). A 401 means the token was rejected; a 404 means the URL does not serve /ingest/verify. Either error, a redirect (which is not followed), or an unreachable URL exits with status 1 before anything runs. A missing token or URL, or a URL that is neither HTTPS nor loopback, exits with status 2.
With a command, it sets AGENTEGRITY_TOKEN and AGENTEGRITY_EXPORTER_URL and replaces itself with your command (execvp). Adapters constructed inside that process attach the HTTPExporter from the environment. A command that cannot be found exits with status 127.
See the CLI reference for all commands.
TypeScript client
The@agentegrity/<framework> packages send every session through the AgentegrityReporter in @agentegrity/client, which speaks the same HTTP API. They read different variables from the Python library:
Requests use
redirect: "error", so a redirect fails the request instead of carrying the token to another address.
The adapter awaits each request before it calls registered exporters and returns. A failed request is passed to onError (by default console.warn) and dropped. There is no queue and no retry. You can pass baseUrl, apiKey, fetchImpl and onError through reporterOptions when you build an adapter with createDefaultAdapter from @agentegrity/client.
The TypeScript packages do not evaluate events. Their events carry evaluation_result: null, and their session summaries report zero attestation records.
What is sent
Streaming sends the full session. The three request bodies are the exporter payloads:POST /sessionscarries the session id, adapter name and agent profile.POST /sessions/{id}/eventscarries one event per request, including itsdatafield. For tool calls that is the tool name and its arguments; for tool results, the tool output; for prompts, the prompt text; forpre_compact, the archived reasoning chain and tool outputs. Evaluated events include the full integrity score with per-layer details.POST /sessions/{id}/endcarries the session summary: counts, chain status,exporters, credential fingerprints and token usage.