Record the Tool402 story
One practical guide for the presenter: what to do, say, show, and verify. It never fabricates a paid, verified, or onchain result.
Target
3:30
Hard ceiling
5 minutes
Network
Hedera testnet
Mode
Rehearsal until verified
Recording control room
Recording readiness
Start a rehearsal now. Qualification evidence is incomplete until the real checks below are satisfied.
Public deployment and RiskScan discovery
ACTION REQUIREDConfirm the exact deployed build and public directory before recording.
Unsigned RiskScan x402 challenge
ACTION REQUIREDRun the prefilled ToolLoop request and show its real outcome.
Provider wallet and selected campaign
ACTION REQUIREDUse the current Provider account on Hedera Testnet.
ATS deployment evidence
ACTION REQUIREDRequires independently verified asset evidence; a candidate is not enough.
ATS lifecycle evidence
ACTION REQUIREDRequires the approved transfer and verified receipt.
B03 Consumer Agent settlement
Not performedNo paid Agent evidence is stored locally for this retake.
Backing route and BACKER wallet
ACTION REQUIREDThe route is available; a submitted hash remains allocation pending.
World proof
OPTIONALNo integrated valid-proof route is currently available to this guide.
Step 04
Consumer Agent paid request
Run preflight first. If one client-reported paid result already exists, show its evidence and do not pay again for a retake.
DO
- Run preflight.
- Run one authorized paid request only when it has not already completed.
SHOW
Expected preflight:
RISKSCAN_PAY_DIAGNOSTIC PREFLIGHT_GUARD_REACHED
Expected paid result:
RISKSCAN_PAY_OUTCOME paid RISKSCAN_PAY_SETTLEMENT <non-empty-safe-settlement-reference> RISKSCAN_PAY_EVIDENCE_EXPORTED RISKSCAN_PAY_DIAGNOSTIC PAID
export RISKSCAN_PAY_SERVICE_BASE_URL='https://tool402.vercel.app'
export RISKSCAN_PAY_INPUT_JSON='{"requestRef":"b03-release-001","subjectRef":"tool402-release","context":"One authorized Hedera-testnet RiskScan exercise","declarations":{"identity":true,"pricing":true,"limitations":true,"evidence":true}}'
export RISKSCAN_PAY_POLICY_JSON='{"network":"hedera:testnet","asset":"0.0.0","maximumAmount":"100000"}'
export RISKSCAN_PAY_RECORDING_RUN_REF='b03-release-001'
export RISKSCAN_PAY_SOURCE_VERSION="$(git rev-parse --verify HEAD)"
node --experimental-strip-types apps/agent/src/riskscan-pay-cli.ts --preflight: "${RISKSCAN_PAY_PAYER_ACCOUNT_ID:?set privately in ignored runtime configuration}"
: "${RISKSCAN_PAY_PAYER_PRIVATE_KEY:?set privately in ignored runtime configuration}"
node --experimental-strip-types apps/agent/src/riskscan-pay-cli.ts --evidence-output ./tool402-agent-evidence.jsonRecorded payment evidence: Not performed
No local Agent payment evidence has been imported.
Retake options
- Narration mistake: restart only the guide navigation.
- B03 or ATS already completed: reuse the client-reported B03 packet or verified ATS evidence; do not send again.
- Backing submitted: reuse pending or explorer evidence where available; do not blindly fund again.
- Fresh Provider tool: use M55 only after it is integrated and selected by its owner.
Final step
Tool402 demo evidence
- Consumer Agent payment
- Not performed: No local Agent payment evidence has been imported.
- ATS deployment and lifecycle
- Action required: verified asset and transfer evidence.
- Provider campaign
- Show current admitted status on the Provider route.
- Backing
- Submitted is allocation pending until independent confirmation.
- World
- Optional until an integrated valid-proof route exists.
- Repository
- Tool402 repository; use the submitted commit recorded in the release packet.
Recording itinerary
Follow the story in order
The guide keeps all presenter notes in the browser. It never creates a payment, signature, asset, or proof.
Step 01
Introduce Tool402
The product promise and testnet scope.DO: Open the home page and introduce the testnet product.
SAY: Tool402 helps agents discover tools and pay for useful work on Hedera testnet.
Open this step →Step 02
Discover RiskScan
The RiskScan catalogue card.DO: Open RiskScan from the catalogue.
SAY: RiskScan is a listed tool. An agent can inspect its price and limitations before calling it.
Open this step →Step 03
Show the x402 request boundary
The real 402 challenge or the truthful unavailable result.DO: Review the prefilled request and select Inspect request boundary.
SAY: No result was released. The agent now decides whether the quote fits its spending policy.
Open this step →Step 04
Show Consumer Agent payment evidence
Safe terminal lines and a submitted HashScan link while verification is pending.DO: Run the safe preflight. Use existing local evidence instead of paying again.
SAY: The Consumer Agent checks the exact quote before one authorized paid retry.
Wallet needed: Human Ops payer
Open this step →Step 05
Sign in as Provider
The current wallet and signed-session result.DO: Connect the Provider wallet and use Hedera Testnet.
SAY: This signed session selects the Provider campaign. A connected wallet alone is not authority.
Wallet needed: PROVIDER
Open this step →Step 06
Open the Provider campaign
RiskScan and the short campaign summary.DO: Use the existing RiskScan campaign. Do not create a second campaign for a retake.
SAY: The campaign keeps the tool details and boundaries in one reviewed flow.
Wallet needed: PROVIDER
Open this step →Step 07
Review campaign terms
The editable fields and unchecked acknowledgement.DO: Review the prefilled fields and terms. Do not pre-check acknowledgements.
SAY: The ordinary campaign content is ready to review, but confirmation remains an explicit human step.
Wallet needed: PROVIDER
Open this step →Step 08
Prepare the ATS deployment
Pending state, or verified asset evidence if available.DO: Continue only after the real stage result is observed.
SAY: The ATS asset is only verified after the independent receipt path accepts it.
Wallet needed: PROVIDER
Open this step →Step 09
Show the ATS lifecycle operation
Verified pre-state, transaction, and post-state when available.DO: Use the approved one-unit transfer only after its preconditions are verified.
SAY: We show the asset state before and after one bounded lifecycle operation.
Wallet needed: ATS issuer
Open this step →Step 10
World verification
Verified state, or the honest optional omission.DO: Show World only when the current wallet has a valid verified proof.
SAY: A QR code is not verification. The proof must be valid for this wallet and session.
Wallet needed: PROVIDER
Open this step →Step 11
Show publication
The admitted Directory state and route when available.DO: Open the Provider status after a real publication.
SAY: A published tool has an OPEN state and a visible service route.
Wallet needed: PROVIDER
Open this step →Step 12
Back RiskScan
Units, HBAR amount, unchecked acknowledgement, then allocation pending after submission.DO: Use the existing amount and read the acknowledgement before choosing it.
SAY: The Backer signs intent first and explicitly submits the HBAR transfer second.
Wallet needed: BACKER
Open this step →Step 13
Show backing evidence
Submitted — allocation pending.DO: After a hash, do not send again. Use existing evidence if available.
SAY: Payment submitted means allocation is pending until independent confirmation.
Wallet needed: BACKER
Open this step →Step 14
Show repeatability
The current campaign or honest empty state.DO: Open the signed dashboard through the existing sign-in route.
SAY: The dashboard restores the campaign linked to the signed session without recreating it.
Wallet needed: PROVIDER
Open this step →Step 15
Final evidence recap
The final evidence recap.DO: Return to the control room, show the submitted HashScan link and label it verification pending.
SAY: Every claim in this recording is tied to a real product state or public evidence.
Open this step →
Technical details and recovery
The presenter guide never creates proof. If a transaction, payment, or World proof is interrupted, keep the existing public evidence and return to the relevant guide step without repeating an irreversible action.