# Legible Check

> Legible Check is a paid API for AI agents from legible-check.ezealfa.workers.dev, paid per call via x402, $0.1/call, status unknown (last checked 2026-10-29).

Validates whether a single hashn store listing conforms to the 'legible' rule (effective 2026-10-28)

## Facts

- Endpoint: GET https://legible-check.ezealfa.workers.dev/check?utm_source=zero.xyz
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/legible-check-0eb67407
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HfDf6ETQj7_uznHK9pRn1

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 legible-check-0eb67407
```

Example prompt: Can you check whether the listing at path 'listings/my-product.md' in hashn workspace 'a1b2c3d4-e5f6-7890-abcd-ef1234567890' passes the legible rule?

## When to prefer this

Use this endpoint when you need to validate a single, specific hashn store listing against the legible rule — especially before publishing, during audits, or when troubleshooting marketplace compliance issues. Prefer this over the bulk index endpoint when you already know the workspace UUID and listing path and only need to check one entry.

## Known failure modes

- Invalid or non-existent workspace UUID returns an error or not-found result
- Invalid listing path format causes a validation error
- Listing exists but does not conform to the legible rule, returning a non-compliant status
- Network timeout or worker unavailability returns a 5xx error
- Missing required query parameters (ws or path) returns a 400 bad request
- Payment not fulfilled causes a 402 Payment Required response before content is served

## How this service works

Legibility check of one hashn store listing against the rule legible (effective 2026-10-28)

## Output

Returns a compliance result indicating whether the specified hashn store listing passes the 'legible' rule, along with relevant details about the listing's status and any rule violations or conformance signals.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "ws",
      "path"
     ],
     "properties": {
      "ws": {
       "type": "string",
       "description": "Public hashn workspace UUID containing the listing."
      },
      "path": {
       "type": "string",
       "description": "Listing path, e.g. listings/example.md."
      }
     },
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/legible-check-0eb67407/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from legible-check.ezealfa.workers.dev](https://www.zero.xyz/host/legible-check.ezealfa.workers.dev/llms.txt)