Pick a consequential request.
An outbound web action is a useful starting point: clear destination, clear method, and a result the team can inspect.
Explore by need
Let agents do the prep.
For agent teams
Let agents do the prep.
Keep the final decision.
Cippax is for teams that want agents to do useful work where one wrong action matters. Start with a single, bounded workflow: the agent proposes, a person approves, and the system executes only that approved action.
Active prototype · selected action paths
ILLUSTRATIVE ACTION FLOW01 / 03
THE AGENTProposes a CRM sandbox write
Target, method, and change are part of the request.
THE PERSONApproves with a passkey
The request waits for a decision on the phone.
THE SYSTEMExecutes once and records it
The approved action is checked before it runs.
A walkthrough, not a live request
The practical starting point
Begin with
one action.
A narrow pilot lets the team test the control boundary before expanding the agent’s reach.
- Who it’s for
- AI platform teams and their security reviewers.
- What you connect
- One outbound HTTP API action in a sandbox, using test data.
- How long it runs
- Timing and acceptance tests are agreed during scoping.
Pilots begin with test data. Sensitive or regulated workflows require a separate review of data handling, hosting, and provider agreements.
Close every other route.
Check how the agent could reach that effect through sockets, credentials, files, or another service. A policy screen alone is not enough.
Exercise yes, no, and failure.
Show what happens after approval, after denial, and when a required witness or audit path is unavailable.
What a pilot should answer
Can it act only
when you meant it to?
01 Can the agent act without using the controlled route?
02 Does the signed approval match the exact action that executes?
03 Can one approval cause a second action?
04 Does the gate close when a required check can no longer be trusted?
Where this stands: A working prototype has demonstrated phone passkey approval and constrained action execution. Guided installation, workflow coverage, and customer-ready verification are still being developed.
Start with a bounded workflow