Watch an unauthorized action stop.
A changed refund. A message to the wrong person. A restricted data export.
See the real authorization decision and what the isolated executor does next.
LOCAL TEST ENVIRONMENT · fixture signing keys, not production evidence.
- 01Connect a model
Use your provider API key, not a Fidacy key.
- 02Define its authority
You set the mandate here, outside the chat.
- 03Ask the agent
Give instructions in your own words.
- 04Inspect the proof
See allow or block, effects and a signed receipt.
3. Ask your agent
Set the authorized recipient in Settings, then ask it to send an email. Try a different recipient to test the boundary. Ordinary questions work too.
An agent response is model text, not evidence of execution. Only the separate Fidacy decision and verified receipt establish authorization; executor effects are reported separately.
Execution details & proof Real events, receipts and browser verification
Start a test. No prerecorded results.
Observed model results
Exact model IDs. No rankings.Inspect receipt and run evidence
Model refusal is not a Fidacy block. Receipt verification checks the signed bytes, not all agent behavior or a production payment. The result event separately reports the isolated executor effect.
No receipt received.
Public key used for this receipt
No signing key received. Only public key material is shown here.
No result event received.