# UUID v3 Validator

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

Validates whether a given string is a valid UUID version 3 (MD5-based namespace UUID)

## Facts

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

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-v3-validator-8e3f8cc7 -d '<json body>'
```

Example prompt: Can you check whether '9125a8dc-52ee-365b-a5aa-81b0b3d4c1c0' is a valid UUID version 3?

## When to prefer this

Choose this endpoint when you need to specifically validate UUID v3 (MD5-based, version bits = 3) format compliance without network dependencies. Prefer the free sandbox endpoint POST /v1/sandbox/id-uuid-v3 first to avoid cost. Use this paid endpoint when the sandbox is unavailable or in production workflows. For other UUID versions use the sibling endpoints (uuid-v1, uuid-nil, nanoid validators).

## Known failure modes

- Empty string input rejected (minLength:1 enforced)
- Input exceeding 20000 characters rejected
- Malformed request body returns error
- Payment failure if USDC balance insufficient or x402 handshake fails

## How this service works

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

## Output

Returns a boolean or structured result indicating whether the provided string conforms to the UUID version 3 (MD5 namespace-based) format specification, including version and variant bit validation.

## 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-3111-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-v3-validator-8e3f8cc7/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)