# Vealth x402-Readiness Check

> Vealth x402-Readiness Check is a paid API for AI agents from vealth.net, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-14).

Analyzes a given URL to determine whether its payment surface is correctly configured, discoverable, and parseable as x402-compliant by an AI agent or registry.

## Facts

- Endpoint: POST https://vealth.net/.well-known/vealth/x402-readiness
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vealth-x402-readiness-check-2e8eac2b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_t7XK3sYrlsBfH1cGkv0f7

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability vealth-x402-readiness-check-2e8eac2b -d '<json body>'
```

Example prompt: Can you check whether https://api.myservice.com is properly set up for x402 payments — I want to know if an agent or x402 registry would be able to discover and pay it today, and what's failing if not?

## When to prefer this

Use this endpoint when you need to programmatically audit whether a specific origin URL is correctly configured for x402 payment discovery — particularly before listing an API on an x402 registry, debugging why an endpoint isn't being indexed, or confirming compliance after making payment-surface changes. Prefer this over manual inspection or generic HTTP auditors because it applies x402-specific checks (e.g. x-payment-info header presence and operation coverage) and returns a structured, agent-readable verdict.

## Known failure modes

- Invalid or unreachable URL returns an error or failed checks
- Site with no x402 headers returns verdict of NOT DISCOVERABLE with all checks failing
- Malformed JSON in response schema if origin is unparseable
- Network timeout if target URL is slow to respond
- False positives if x402 headers are present but malformed

## How this service works

Find useful work. Build a life from it. Every job shows the place, the task, the proof, and the pay before you begin. Start today and grow toward mastery.

## Output

Returns a JSON object with an origin, product name, a plain-language verdict ('DISCOVERABLE', 'NOT DISCOVERABLE', etc.), and a list of named check results (e.g. 'x-payment-info') each with a status (pass/fail) and detail message explaining what was found or missing.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "origin": "https://example.com",
  "product": "x402-readiness",
  "verdict": "NOT DISCOVERABLE — an x402 registry reading this origin today would index nothing.",
  "findings": [
   {
    "check": "x-payment-info",
    "detail": "23 operation(s), none declare x-payment-info.",
    "status": "fail"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vealth-x402-readiness-check-2e8eac2b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from vealth.net](https://www.zero.xyz/host/vealth.net/llms.txt)