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
IdentityDiscovers 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.
Microsoft 365 audit
IdentityWill 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.
Direct HTTP stream
Direct streamOne 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.
Node SDK
Direct streamDrop-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.
OpenTelemetry exporter
Direct streamOne-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.
MCP server
Read accessYour AI assistant reads the verified evidence directly. Ask "what did agent X do last week?" in plain language, get answers from signed 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.
Langfuse
ImportBulk-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.
LangSmith
ImportImport 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.
Salesforce
TelemetryEvent 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.
ServiceNow
TelemetrySystem 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.
AWS IAM
IdentityIAM 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.
Google Cloud
IdentityService 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.
Kubernetes
TelemetryPod-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.
CI/CD pipelines
TelemetryDeployment 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.
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.
