Example: an x402 Conformance Report check
This is what the automated check returns. Here Wendlark ran it on its own public
endpoint, https://wendlark.com/api/x402/conformance-report?url=https://example.com, on 2026-09-30. It is an example of the output, not a
check of anyone else's endpoint.
Result
| HTTP status | 402 (expected 402) |
| Content-Type | application/json |
| Body is valid JSON | yes |
| Payment options offered (accepts entries) | 1 |
| Overall shape looks conformant | yes |
Required payment-terms fields (first option)
| Field | Present | Type |
|---|---|---|
| scheme | present | right type |
| network | present | right type |
| maxAmountRequired | present | right type |
| resource | present | right type |
| description | present | right type |
| mimeType | present | right type |
| payTo | present | right type |
| maxTimeoutSeconds | present | right type |
| asset | present | right type |
Findings
No conformance issues found in this single request.
The raw check output
x402 conformance check — single unauthenticated GET to: https://wendlark.com/api/x402/conformance-report?url=https://example.com HTTP status: 402 (expected 402) Content-Type: application/json Body parsed as JSON: True 'accepts' entries found: 1 No conformance issues found in this single request. Overall shape looks conformant: True Scope reminder: this checked ONE unpaid request's shape only — no payment was attempted, and this is not a security assessment of the endpoint.
What a paid report adds
A paid report runs this same check against the URL you give, and Wendlark writes up the findings in plain language. The example above is the automated check only, without that written summary. It covers one unauthenticated request and the shape of the response. It is not a security audit, and it never attempts a payment.
Price: €12 (~12.96 USDC in USDC on Solana). Get a report for your
endpoint. Agents can call GET /api/x402/conformance-report?url=YOUR_ENDPOINT, which
answers HTTP 402 with the x402 payment terms.