Connectors

Identity systems tell you who the agents are. Telemetry sources tell you what they did. Provantix joins them into one attributable chain, here is every way in.

Entra ID

Identity

Discovers service principals, app registrations and agent identities from your Microsoft tenant.

Pulls sign-in and directory events through Microsoft Graph. Every workload identity, including the ones no one registered, becomes a first-class agent record with an owner and a lifecycle. In validation with early-access tenants before general availability.

entra id, sample streamBeta
09:41:02entra: service-principal discovered svc-sre-bot (appId 7f3c…d21a)
09:41:03entra: sign-in validated, credential: certificate (thumbprint 88:AB…)
09:41:04agent identity bound → owner: [email protected]

Microsoft 365 audit

Identity

Will correlate agent activity with Exchange, SharePoint and Copilot interaction records.

In development: Purview backfill plus forward collection to close the gap between what an agent's identity touched and what your collaboration estate recorded, the pairing that makes attribution provable.

microsoft 365 audit, sample streamRoadmap
m365: connector in development (Purview audit API)

Direct HTTP stream

Direct stream

One POST endpoint per organization, reached by outbound HTTPS from your code, no inbound access to your network.

Each organization gets an isolated emitter key. Payloads are signed with the key at capture and verified before storage, so the integrity chain starts on your side, not on our servers. Ship from curl, any HTTP client, or the Node SDK.

direct http stream, sample streamAvailable
09:44:00POST /v1/batches, 214 records accepted, signatures verified (org versalence)
09:44:00attribution: 214/214 events bound to known agents
09:44:01finding raised: shared credentials across 2 agents

Node SDK

Direct stream

Drop-in wrapper that captures tool calls, model I/O and session metadata automatically.

A few lines wrap your agent framework. The SDK batches, retries and signs payloads so telemetry survives flaky networks without touching your request path. Public package publishing is in progress; the Python SDK is on the roadmap.

node sdk, sample streamBeta
09:45:30sdk: session started agent=sre-bot run=01H8…
09:45:31sdk: tool_call kubectl.scale captured (latency 412ms)
09:45:31sdk: payload signed, queued for delivery

OpenTelemetry exporter

Direct stream

One-line instrumentation for agents already emitting OTel GenAI spans.

Point your existing OpenTelemetry setup at Provantix with the @provantix/otel-exporter package — standard GenAI instrumentations flow through the same signing, chain and attribution pipeline as the SDK, no agent code changes. Latency and spool benchmarks are published in the package.

opentelemetry exporter, sample streamAvailable
09:46:10otel: exporter attached to tracer provider
09:46:11otel: gen_ai spans mapped → AAR records
09:46:11otel: batch signed, custody chain extended

MCP server

Read access

Your AI assistant reads the verified evidence directly. Ask "what did agent X do last week?" in plain language, get answers from sealed records.

Connect Claude, ChatGPT, Cursor or VS Code over the Model Context Protocol. Every tool is read-only, results are paged and summarized by our database (never by the model), people appear as pseudonymous handles, and every read is audited and revocable in Settings. A new connection reads evidence, findings and coverage. Cost is a separate switch an admin turns on, and each connection gets cost only after it asks for it and the person approves. From the Pilot plan up.

mcp server, sample streamAvailable
10:05:00mcp: assistant connected (org versalence, scopes evidence:read findings:read coverage:read)
10:05:02summarize_activity: 1,214 records across 3 agents, 7 days
10:05:03audit: call recorded (user, client, tool, args hash)

Langfuse

Import

Bulk-import existing traces and sessions. Your history becomes attributable evidence on day one.

Point Provantix at your Langfuse project and we replay traces into the same evidence model as live telemetry, no re-instrumentation, no data loss.

langfuse, sample streamAvailable
10:02:10langfuse: import started, project cruzclaw
10:02:44langfuse: traces mapped → agent sessions
10:02:45attribution: sessions bound to identities

LangSmith

Import

Import LangSmith runs and datasets for teams standardizing on the LangChain ecosystem.

Planned: runs, feedback and dataset rows will land in the same chain-of-custody model, so mixed estates (Langfuse + LangSmith + direct streams) report through one pane.

langsmith, sample streamRoadmap
langsmith: connector in development

Salesforce

Telemetry

Event Monitoring and SetupAuditTrail correlation for agents acting inside your CRM.

Closes the loop for revenue-ops agents: every record touch, permission change and API call attributed back to the agent identity that initiated it.

salesforce, sample streamRoadmap
salesforce: connector in development (Event Monitoring API)

ServiceNow

Telemetry

System Log and audit correlation for ITSM agents and virtual agents.

Maps agent-driven incident changes to the requesting identity, so automated remediation carries the same evidence burden as a human change request.

servicenow, sample streamRoadmap
servicenow: connector in development (REST Table API)

AWS IAM

Identity

IAM roles, instance profiles and access keys behind your agent workloads, attributed to their owners.

Planned: CloudTrail and IAM correlation so agents running on AWS carry the same identity binding as Entra-registered workloads.

aws iam, sample streamRoadmap
aws: connector on the roadmap (CloudTrail + IAM)

Google Cloud

Identity

Service accounts and workload-identity federation for agents running on GCP.

Planned: service-account inventory and audit-log correlation, so multi-cloud estates report through one evidence chain.

google cloud, sample streamRoadmap
gcp: connector on the roadmap (Audit Logs + IAM)

Kubernetes

Telemetry

Pod-level agent attribution for agents running in your clusters.

Planned: workload-identity and audit-log correlation so an agent's actions are bound to the service account and namespace that launched it.

kubernetes, sample streamRoadmap
kubernetes: connector on the roadmap (audit + workload identity)

CI/CD pipelines

Telemetry

Deployment and automation runners as first-class agent identities.

Planned: GitHub Actions, GitLab and similar runners registered as agents, so pipeline-driven changes enter the same chain of custody.

ci/cd pipelines, sample streamRoadmap
cicd: connector on the roadmap (runner identity)

Your agents are already acting.
Start proving who authorized them.

Early-access organizations get a dedicated database, identity connectors, and a guided import of their existing traces.

Invite-only during early access. Google Workspace SSO supported from day one.