Wasit runs the real payment flow against your service and verifies the on-chain settlement itself, not just whether the response looks right.
$ npx @wasit-dev/cli test --target <your-service-url>The same request, checked two different ways.
Wasit talks to two things: your service, over HTTP, and Stellar, over RPC. It never trusts the first about what happened on the second.
Step 5 is the point of the tool. A receipt only proves a service claims to have been paid; the chain proves it actually happened. Full flow in the docs →
The things people usually ask before running it.
Read-only checks are free. Checks that spend or mutate state are opt-in and clearly flagged before they run.
Destructive checks require an explicit flag and only run against a channel you name as disposable. Wasit is built for Stellar testnet.
Same core, two interfaces. The CLI runs from your terminal or a CI job; the MCP server exposes the same checks as tools an agent like Claude Code can call directly.
No signup. Run the install command directly with npx — a private key is only needed for checks that touch a payment or channel.
The Check Catalogue in the docs lists every check, what it asserts, and which spec or SDK version it was verified against.
Yes — Apache-2.0, full source and Check Catalogue on GitHub.
Point it at your service and get a pass/fail report backed by on-chain verification. No signup, no config file required to start.
$ npx @wasit-dev/cli test --target <your-service-url>Open source · Testnet only · No signup required