Prepare a RiskScan Provider campaign
A route-by-route guide to the current five-step wizard, issuer-controlled ATS preparation, and the evidence required before a campaign can be OPEN.
01 · Provider status
Read the current local surface
The Provider overview is read-only. It reflects admitted campaign records and does not itself change a campaign.
/provider/deploy to work through the campaign wizard. A missing record, command bridge, or accepted authority leaves the corresponding step unavailable.02 · Five steps
Follow the campaign wizard
The first four steps contain the current editable fields. Review and sign is a non-editable review surface; signed durable values cannot be changed from that review.
- Step 01
Tool details
Set the title, category, one-line description, and customer problem for the offering draft.
- Step 02
Interface and capability
Set the qualifying resource and capability summary; the declared capability remains fixed.
- Step 03
Pricing and target agent customers
Set advertised tiers and target customers. The live x402 requirement remains the payment authority.
- Step 04
Funding and revenue-note terms
Record use of funds, risks, and acknowledgement. The v1 economics and revenue-note parameters are fixed for the offering version.
- Step 05
Review and sign
Review the non-editable summary before requesting the separately gated deployment-stage signatures.
03 · Control boundary
Issuer and ATS stages
The review uses an issuer wallet on Hedera Testnet, chain 296. The current stage rail is: Record the draft offering; Prepare asset creation (ATS_CREATE); Create the revenue note in MetaMask and attach its returned candidate; then Publish to the Tool Directory.
Prepare asset creation records an external preparation before any wallet transaction. The revenue-note action and directory publication each need their own accepted inputs and receipts.
04 · Control boundary
Do not infer deployment from a signature
A review or signature is not an ATS deployment. A relayed accepted signature is not an on-chain fact, and a prepared record is not a created revenue note.
The directory becomes OPEN only after the full staged path and corroborated receipt conditions are met. Until then, the relevant handoff remains unavailable or blocked.
05 · Continue locally
Choose a local next step
Read the current provider projection.
Open ProviderContinue through the existing RiskScan provider wizard and its stage rail.
Open campaign deploymentReturn to the current RiskScan detail route.
Open RiskScanContinue through the local product tour.
Open guided demo