# UUID v5 Validator

> UUID v5 Validator is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.007/call, status unknown (last checked 2026-10-02).

Validates whether a given string is a properly formatted UUID version 5 identifier

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/id-uuid-v5?utm_source=zero.xyz
- Price: $0.007/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/uuid-v5-validator-d9f398fc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7G-acdPypino7qI4h_9yo

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 uuid-v5-validator-d9f398fc -d '<json body>'
```

Example prompt: Can you check if this string is a valid UUID v5: '6ba7b810-9dad-11d1-80b4-00c04fd430c8'?

## When to prefer this

Use this endpoint when you need a definitive, server-side UUID v5 format check without building your own regex or RFC 4122 parsing logic. Prefer the free sandbox endpoint POST /v1/sandbox/id-uuid-v5 first; use this paid endpoint when the sandbox is unavailable or you need production-grade reliability with SLA guarantees. Best suited for data pipelines, API validation middleware, or agent workflows that must confirm identifier provenance.

## Known failure modes

- Empty or missing value field returns validation error
- String exceeding 20000 characters rejected
- Malformed request body returns 400
- Payment failure or insufficient USDC balance returns 402
- UUID v1, v3, v4, or v7 strings correctly return invalid for v5 check

## How this service works

Call when an agent needs whether a string is a valid uuid-v5. No network. Exact $0.007 USDC. Prefer unpaid POST /v1/sandbox/id-uuid-v5 first.

## Output

A boolean or structured result indicating whether the input string conforms to the UUID v5 format, including correct version (5) and variant bits as specified by RFC 4122

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "description": "JSON value for schema-check SKUs. Omit it on string checks such as email or IBAN."
  },
  "value": {
   "type": "string",
   "examples": [
    "11111111-1111-5111-8111-111111111111"
   ],
   "maxLength": 20000,
   "minLength": 1,
   "description": "Value to check. The route description names the format: email, phone, IBAN, postal code, VAT, national id, or similar."
  },
  "schema": {
   "description": "JSON Schema document for schema-check SKUs. Omit it on string checks."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/uuid-v5-validator-d9f398fc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentshelf.syntexa.ch](https://www.zero.xyz/host/agentshelf.syntexa.ch/llms.txt)