Integrations
Built to read from the systems your agents already touch
ThetaLayer reads agent runtimes, systems of record, cost sources and your directory — read-only, through the exports and audit logs they already produce. No proxy, and no changes to your agents.
Connector availability is confirmed during pilot scoping. Product names are trademarks of their owners; they're listed as examples of systems ThetaLayer is built to read from and don't imply partnership or endorsement.
- RuntimeRun IDs · doc refsIn-house orchestratorOpenTelemetry GenAI spans
- RuntimeNo doc refsVendor agent platformSession + billing export
- RecordConnectedERPChange documents
- RecordConnectedERPPayment runs
- RecordConnectedApprovalsTasks and decisions
- RecordConnectedMailboxAccess and send audit
- IdentityIdentity mapDirectoryPeople and service principals
What we read from
Four kinds of source, one contract
Every source maps to the same canonical events, so an agent on a vendor platform and one in your own orchestrator are measured with the same definitions.
Agent runtimes
What agents claim they did: runs, model calls, tool calls, delegation to sub-agents, and what each step cost.
- Run start and end, with status and reason
- Model calls with model, tokens and price reference
- Tool calls with operation, target and result
- Delegation to sub-agents, and platform credits
Systems of record
What actually changed — the independent evidence every agent claim is checked against.
- Change documents and field-level audit trails
- Approval requests and decisions
- Payment runs and their outcomes
- Mailbox and workbook access and send events — never content
Cost sources
What it cost — metered where the source allows, allocated where it doesn't, and always labeled as which.
- Metered: tokens × price, or credits × credit price, per run
- Allocated: platform fees and seat licenses spread across runs
- Sub-agent cost rolled up into the parent run
Identity
Who is who — so a technical ERP user, a service principal and a clerk's delegated token resolve to the right agent or person.
- People, groups and service principals
- Technical accounts in systems of record
- Agent identities versus delegated human credentials
Connector availability is confirmed during pilot scoping. Product names are trademarks of their owners; they're listed as examples of systems ThetaLayer is built to read from and don't imply partnership or endorsement.
Per source
What we use from each source — and what never leaves
Each adapter keeps only the facts needed to reconcile and measure. Sensitive values are hashed with a key that stays in your network; free text is dropped before export.
| Source | Used as evidence | Hashed | Dropped before export |
|---|---|---|---|
| Agent runtime spans | Run and step IDs, tool and operation, result, model and token counts, identities | Supplier invoice numbers → invoice_key | Prompts and completions, tool arguments and results |
| Vendor platform exports | Sessions, actions and results, retries, credits | Supplier invoice numbers, message IDs | Action inputs and outputs |
| ERP change documents | Document and vendor references, amounts, transaction code, channel | IBANs, supplier invoice numbers | Item texts, vendor names, VAT IDs |
| Mailbox audit | Access and send events, message references, recipient domain | Internet message IDs | Subjects, bodies, email addresses, client IPs |
| Workbook audit | Row-appended events and row references | Invoice numbers in cells → invoice_key | Cell values |
| Approvals | Request, decision, approver, approval type, amount | Supplier invoice numbers, new bank details | Approval comments |
| Payment runs | Paid, blocked or reversed; payment document, date, amount | — | — |
Sits alongside
Works next to the tools you already govern agents with
ThetaLayer doesn't replace vendor control planes or security tooling. It reads across them and adds what none of them hold alone: the link between what each agent did, what it cost, and what your systems of record show.
Catalogs and governs agents inside the Microsoft ecosystem.
Evidence from outside it — your ERP, CRM and approvals — and cost per outcome comparable with other vendors' agents.
Governs AI agents and workflows, centered on the ServiceNow platform.
Reconciliation against systems of record beyond the platform, and one scorecard across every vendor.
Protect against prompt injection, data leakage and risky permissions.
Whether each agent stayed within its business mandate, and what it produced for what it cost.
Collects security events for detection and response.
Agent-level context — the run, the mandate, the evidence — for the exceptions your security team needs to see.
Runs, evidence chains, scorecards, mandates and the review queue.
Runs, links, mandate checks and review decisions, for internal audit and GRC tools.
Exceptions pushed to your ticketing, chat or SIEM as they're raised.
New connectors
How a new connector gets built
Connectors are small by design: an adapter reads one source and maps it to the contract. Everything downstream — linking, mandates, scorecards — works unchanged.
Days, not months, for systems that already keep an audit log or change history.
Scope and timing are confirmed for each source during pilot scoping.
- 01AdapterA small, versioned reader for the system's native export or audit API, running in your collector with read-only credentials.
- 02Map to the contractRecords become canonical events: object references, business keys, identities and allow-listed attributes only.
- 03ValidateSchema validation, a raw-versus-exported preview for your security team, and reconciliation against records you already know.
- 04ShipThe adapter version is stamped on every event as provenance, so any figure traces back to the code that produced it.
If an agent writes to a system that keeps an audit log, ThetaLayer can account for it.
Book a Demo
Bring your agent stack to the demo.
Tell us which runtimes and systems of record your agents touch. We'll show how they map to one contract — and confirm connector availability while scoping a six-week, read-only pilot.