Governed Voice AI for agencies in regulated verticals
AI can bind your business.
One vendor, one contract and one invoice. The mandate sets the ceiling, the scope and the expiry before the AI can act, and what crosses the line stops and goes to a person.
€1,497 once, then €499 a month
Founding price for the first three external agencies. 5,000 minutes included.
Audact boundary
Every request routed through the governed workflow
is evaluated against the active mandate
Inbound sales calls · max €150 discount per order · to 31 Dec 2026
Discount refused · nothing promised to the caller
Decision requiredThe agent held the quote at list price and passed the discount to a person.
Inbound sales calls · current
€150 discount per order
€400 asked · escalate
No discount released
None created
Follows closure evidence, not a status field
Voice
Resell governed voice AI under your own brand.
One vendor, one contract, one invoice.
€1,497 once, then €499 a month
Founding price for the first three external agencies.
Germany: national policy layer verified. Netherlands: in progress.
Control
Decide what a governed AI action may cause on the company's behalf before it runs.
Not on sale yet. What is available today is a conversation about your authority model, and a non-binding scope.
Two layers, one application
Decide what an AI may cause, on whose behalf and within which limits.
Enforced when it acts, not reviewed afterwards.
What was decided and what followed from it stays recomputable, months later.
When it is questioned later, the record answers, not memory.
Built on Control and Proof
Real-time voice agents that stay inside the mandate and leave a receipt.
In a conversation the commitment is made before anyone can review it.
Don't take our word for it
Three of its values recompute in your own browser, with the browser's own SHA-256. No key, no account, and nothing is sent to us.
Open the receipt explorerCompliance receipt
Worked exampleRCP-901
Recomputable without a key
Inclusion in the Merkle root
In developmentPublication of the roots, and the open endpoint that serves them, is in development; the fourth check follows once they are published.
