Discover / verza.dev
verza
□ No challenge detectedSouth African verification primitives for AI agents: identity and VAT number validation, and NCA credit-agreement lawfulness checks against the Regulation 42 interest caps. CIPC company lookup in development. Paid per call via the x402 protocol (USDC on Base). No accounts, no API keys.
- Challenge detected
- 0 of the last 3 checks
- Last checked
- 16 Oct, 23:40 UTC
- In our index since
- 14 Oct 2026
Endpoint
curl -i https://verza.dev # 402 Payment Required: pay with an x402 client (USDC on Base), # then send the same request again with the payment attached.
Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/verza.dev
Recent checks
14 Oct 2026One bar per check, showing up to 20 recent checks. Coloured bars show relative response time, with a minimum visible height; full-height grey bars mean no challenge was detected. “Challenge detected” means HTTP 402 or another detected payment-challenge signal.16 Oct 2026
All 3 checks
| When (UTC) | Result | HTTP | Response |
|---|---|---|---|
| 16 Oct, 23:40 UTC | No challenge detected | 200 | 895ms |
| 15 Oct, 17:07 UTC | No challenge detected | 200 | 917ms |
| 14 Oct, 08:45 UTC | No challenge detected | 200 | 791ms |
Questions
Did our last probe detect a payment challenge?
No. At our last probe on 16 Oct, 23:40 UTC, we detected no payment challenge.
What payment terms does verza advertise?
The listing advertises x402, Base and USDC. Check the seller's current payment challenge and authentication requirements before paying.
Where is verza listed?
In x402-list.com. Superstables first indexed it on 14 Oct 2026.
Something wrong on this page? Tell us.