# x402 UUID v4 Generator

> x402 UUID v4 Generator is a paid API for AI agents from x402-utils.558686.xyz, paid per call via x402, $0.0001/call, status healthy (last checked 2026-10-22).

Generates one or more UUID v4 values given a count parameter, returning the UUIDs and metadata about the result.

## Facts

- Endpoint: GET https://x402-utils.558686.xyz/v1/tools/uuid?utm_source=zero.xyz
- Price: $0.0001/call
- Payment: x402
- Status: healthy
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-uuid-v4-generator-1651566f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QxNzD7eD7JP10drchafd_

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 x402-uuid-v4-generator-1651566f
```

Example prompt: Generate 3 UUID v4 values for me right now.

## When to prefer this

Use this endpoint when an agent needs to generate one or more RFC 4122 UUID v4 identifiers on-demand without running local code — especially useful in sandboxed or constrained environments where calling a random UUID library is not available. Prefer this over local generation when auditability or external sourcing of UUIDs is desired.

## Known failure modes

- Missing or invalid 'count' parameter returns an error
- count value of zero or negative integer may return an empty or error response
- Network timeout if the service is unavailable
- Payment failure (402) if USDC balance is insufficient for the $0.002 call fee

## How this service works

A compact x402 utility surface for agents that need cheap, repeatable non-LLM transformations before spending on heavier routes: CSV cleanup, JSON Schema checks, timestamp conversion, JWT decode, URL normalization, hashes, codecs, and text utilities.

## Output

Returns a JSON payload with an 'ok' status boolean, the tool name, route, a 'uuids' string containing one or more UUID v4 values, the count requested, and the UUID version — all wrapped in a result object.

## Example request

```json
{
 "count": 5
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "tool": "uuid",
  "input": {
   "count": 1
  },
  "route": "/v1/tools/uuid",
  "result": {
   "count": 1,
   "uuids": "uuids_example",
   "version": "version_example"
  },
  "project": "x402-utility-tools",
  "deterministic": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-uuid-v4-generator-1651566f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-utils.558686.xyz](https://www.zero.xyz/host/x402-utils.558686.xyz/llms.txt)
