Support investigations
Give reviewers a consistent record to examine when an agent action is disputed. Connect it to your authorization and execution logs.
← All productsAgents act.
04 / Agent Attestation · EARLY ACCESS
Agents act.
Keep the evidence.
Signed action records with an external anchoring trail. Commit to what your agent recorded while keeping the underlying action payload in your infrastructure.
Discuss the pilotFor agent-platform builders and security teams · Early access
EXPLORE THE WORKFLOW
Capture the action at its source
Your system creates a canonical action record, hashes it and signs the commitment with the agent’s key.
Action · stays with you
- agent
- Support assistant
- action
- Change customer plan
- customer
- person_7f2a
Commitment
- payload
- Hash of canonical action
- identity
- Agent signature
Keep the source record available for later comparison with the commitment.
Interactive illustration · Fictional data · No live requests
A record counterparties can check later.
Signed records · Hash anchoring · Testnet pilotWHY THIS LAYER
An action with a checkable record.
Keep payloads local
The workflow submits a hash and signature. Decide separately how original records are stored, retained and disclosed for a review.
Build verifiable history
Explore how signed actions and counterparty confirmations can inform an agent’s history. Review what each signal actually establishes.
TECHNICAL EVALUATION
What does the evidence establish?
Define the evidence for your pilot before making a production decision.
Recorded payload
Retain the original action and its canonical representation in your environment.
Recompute the commitment and compare it with the recorded hash.
Identity & inclusion
Review the agent signature and the proof against the referenced anchor.
Inspect the existing pilot verifier and follow the transaction to the testnet explorer.
Operational limits
The published offering is an early-access testnet pilot.
Agree on signing-key handling, retries, anchoring delays and unavailable evidence.
FROM INTEREST TO INTEGRATION
Start with one agent action.
Define success for one workflow before expanding the scope.
Plan it with an architect- 01
Choose a meaningful action
Identify the event, its authorization and the exact moment it should be recorded. Define a stable canonical representation.
- 02
Instrument a test agent
Keep signing keys protected. Plan retries, duplicate handling and how to preserve the original evidence.
- 03
Review a pilot record
Check signatures and inclusion with a counterparty. Test disputed and incomplete records before depending on the trail.
BEFORE YOU INTEGRATE
The questions
worth asking.
EARLY ACCESS · TESTNET PILOT
Discuss pilot access
Describe your agent and one action you need to investigate or verify. Review whether the current pilot fits.
Request pilot accessOpens the access form on provyn.cloudsales@provyn.cloud