# LUMI Verifier — x402 Endpoint Lint

> LUMI Verifier — x402 Endpoint Lint is a paid API for AI agents from app.tenna.ai, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Validates a 402 Payment Required response body for x402 compliance, reporting payability, Bazaar catalogue opt-in, and machine-readable schema presence with JSON evidence paths for every defect.

## Facts

- Endpoint: POST https://app.tenna.ai/api/x402/verifier/x402_endpoint_lint
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lumi-verifier-x402-endpoint-lint-bb51b25b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zI3TH_8leyeJv0dgV0gMg

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 lumi-verifier-x402-endpoint-lint-bb51b25b -d '<json body>'
```

Example prompt: Can you lint this 402 Payment Required body my endpoint returns and tell me if it passes x402 compliance — check whether it's payable, opted in to the Bazaar, and whether a buying agent can read the input schema? Here's the body: {"accepts":[{"scheme":"exact"}],"resource":{"url":"https://example/api","description":"what it sells"},"x402Version":2}

## When to prefer this

Choose this endpoint when you need to validate an x402 402 Payment Required response body for protocol compliance before publishing to the Bazaar catalogue, before an agent attempts payment, or when debugging why a listing was rejected. It is a static linter — it does not make payments or call the target endpoint — so it is safe to run in pre-flight checks without financial risk. Prefer this over manual inspection when you need machine-readable defect evidence paths.

## Known failure modes

- Malformed or missing paymentRequiredBody causes validation error
- Incorrect offering identifier (not exactly 'x402_endpoint_lint') results in rejection
- Supplying a non-402 response body may produce misleading lint results
- A PASS result does not guarantee correctness or accuracy of the underlying service

## How this service works

x402 Endpoint Payment Check. Check an x402 endpoint's 402 payment-required body before you rely on it. Reports whether the contract is payable, whether it is opted in to the Bazaar catalogue, and whether a buying agent can read its input schema by machine. Every defect carries a JSON evidence path. Reads the body you supply; it does not pay or call the endpoint. A PASS is not a correctness guarantee and not a claim that the service is accurate.

## Output

A structured compliance report indicating PASS or FAIL, with individual findings for payability, Bazaar catalogue opt-in status, and machine-readability of the input schema. Each defect is accompanied by a precise JSON evidence path pointing to the offending field in the supplied 402 body. The linter does not make a payment or call the target endpoint.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "offering": {
   "type": "string",
   "const": "x402_endpoint_lint",
   "description": "Offering identifier. Must be exactly 'x402_endpoint_lint'."
  },
  "paymentRequiredBody": {
   "type": "object",
   "examples": [
    {
     "accepts": [
      {
       "scheme": "exact"
      }
     ],
     "resource": {
      "url": "https://example/api",
      "description": "what it sells"
     },
     "x402Version": 2
    }
   ],
   "description": "The JSON body the endpoint returned with HTTP 402, verbatim."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lumi-verifier-x402-endpoint-lint-bb51b25b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from app.tenna.ai](https://www.zero.xyz/host/app.tenna.ai/llms.txt)