# neo x402-lint

> neo x402-lint is a paid API for AI agents from neo-collettive.onrender.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-29).

Lints an x402 payment-required endpoint by checking body vs header field consistency, EIP-55 address checksums, and method conflicts — returning a signed, logged findings report.

## Facts

- Endpoint: POST https://neo-collettive.onrender.com/x402/x402-lint?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/neo-x402-lint-f31fb3f2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RH_n13wm-p3Qw7hbOy4c6

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 neo-x402-lint-f31fb3f2 -d '<json body>'
```

Example prompt: Can you lint my x402 endpoint at https://api.mystore.com/premium-data using GET and tell me if there are any header/body mismatches, bad EIP-55 checksums, or method conflicts?

## When to prefer this

Choose this endpoint when you need a signed, logged audit of an x402 payment-required endpoint's correctness — specifically for catching EIP-55 checksum errors, header/body field mismatches, and GET/POST method conflicts. Prefer it over manual inspection or generic HTTP debuggers when you need a verifiable, cryptographically signed report suitable for marketplace listings or compliance records.

## Known failure modes

- Target URL is unreachable or times out — returns an error indicating the endpoint could not be fetched
- Target URL does not return a 402 response — findings may be empty or indicate missing payment-required headers
- Invalid URL format in request body — returns a validation error
- Method enum value outside GET/POST — rejected by schema validation
- Target endpoint behind SSRF-protected network — may return access-denied or timeout

## How this service works

Lint a seller's unpaid 402: body vs PAYMENT-REQUIRED header fields, EIP-55 checksums, method conflicts. One unpaid read, never pays. Signed, logged result.

## Output

A JSON object containing: an error count (integer), a findings array listing each detected issue (field name, issue type, description), and a cryptographic signature over the result for audit trail purposes. The endpoint makes one read-only fetch of the target URL without paying, so the seller's gate is never triggered.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string"
  },
  "method": {
   "enum": [
    "GET",
    "POST"
   ],
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "errors": 0,
  "findings": [],
  "signature": "..."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/neo-x402-lint-f31fb3f2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from neo-collettive.onrender.com](https://www.zero.xyz/host/neo-collettive.onrender.com/llms.txt)