Audit your AI agents before your auditors ask you to.
Sigmodx gives finance teams a cryptographic audit trail for every AI agent decision, without touching your underlying data. We're running a structured pilot program for Q3 2026. 4 spots remaining.
The pilot
- Duration
90 days
- What you get
- One AI agent fleet fully instrumented
- Append-only decision log, live from day one
- Human reviewer queue for your team
- Weekly reliability signal reports
- Attestation package at end of quarter, ready for your auditors
- One verification string your auditors can independently confirm at sigmodx.com/verify
- What we need
- One AI agent or fleet with a defined decision workflow (invoice approval, anomaly detection, trade execution, or similar)
- One internal point of contact (finance, audit, or compliance team)
- Willingness to share feedback on what auditors actually ask for
- Cost
No charge for pilot participants. Pricing for continued access is agreed at pilot completion based on agent count and scenario coverage.
- Commitment
90 days. No contract beyond the pilot period.
Pilot participants help shape what "AI agent audit infrastructure" means in practice. The invoice approval scenario was built with direct input from early design conversations. If you have a workflow that isn't covered, we want to hear about it.
Before you fill in the form
No. Sigmodx operates on cryptographic hashes of agent input payloads, not the underlying data. Your invoices, GL records, and vendor data never leave your environment. Sigmodx stores the hash, the decision, the rationale, and the outcome. Your auditors verify the hash. That is the entire data footprint.
Instrumentation is a lightweight SDK call. Python and TypeScript packages are available. An agent that currently approves invoices without logging can be instrumented in an afternoon. No infrastructure changes, no new databases, no vendor access to your internal systems. If you use EmbiPay for agent economic execution, cinmon-control handles the state enforcement automatically.
A verification string is a short alphanumeric identifier like SIGMODX-INVOICE-E54ECE50-D331D86614C1. Your auditors submit it to sigmodx.com/verify and receive cryptographic confirmation that the audit record is intact and unaltered. They get proof without seeing your data. You keep the underlying records internally and produce them directly to auditors if required. Sigmodx is the proof layer, not the data layer.
What happens after you submit
Intro call (Week 1)
30 minutes. We confirm your agent workflow, identify the right scenario (invoice approval, anomaly detection, trade execution, or forecast generation), and agree on what a useful attestation package looks like for your auditors.
Instrumentation (Week 1–2)
Your team adds the Sigmodx SDK to your agent. We provide integration support. Decision logging goes live. You see your first decision events in your org dashboard within hours.
Active period (Weeks 2–12)
Decisions log continuously. Your team uses the reviewer queue to assess a sample of agent decisions, typically 30–60 minutes per week. Reliability signals update automatically. You can see your agent's ALLOW/LIMIT/BLOCK state in real time.
Attestation (Week 12)
We generate the attestation package for the quarter. You receive a verification string for each attested period. We walk through what to give your auditors and how the verification endpoint works.
Request pilot access
Sigmodx is built by Cinmon. The audit infrastructure described on this page is live in production. Not a roadmap. The invoice approval scenario is available now. Trade execution and anomaly detection scenarios are in active development. Questions: support@sigmodx.com.