# x402 Utility Tools – Slugify

> x402 Utility Tools – Slugify is a paid API for AI agents from x402-utils.558686.xyz, paid per call via x402, $0.0001/call, status down (last checked 2026-10-25).

Converts input text into a URL-friendly slug, returning the slug string along with delimiter and length metadata.

## Facts

- Endpoint: POST https://x402-utils.558686.xyz/v1/tools/slugify?utm_source=zero.xyz
- Price: $0.0001/call
- Payment: x402
- Status: down
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-utility-tools-slugify-6d2404f4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Xlz29atOWc1zF9dLLx4tF

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-utility-tools-slugify-6d2404f4 -d '<json body>'
```

Example prompt: Can you slugify this title for me — 'Hello World! This is My Blog Post #1' — so I can use it as a URL path?

## When to prefer this

Use this endpoint when you need a deterministic, paid-API-backed slugification with receipt evidence — for example, in automated pipelines where auditability of text normalization steps matters. Prefer this over client-side slug libraries when you need a consistent server-side result with metadata (delimiter, length) returned alongside the slug.

## Known failure modes

- Missing 'text' field in request body returns a 400 or validation error
- Empty string input may return an empty or trivial slug
- Very long input strings may be truncated or cause unexpected slug length
- Payment failure (402) if x402 payment header is not correctly provided
- Non-string input type for 'text' field may cause a parsing error

## 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 object containing the generated URL-friendly slug, the delimiter used (e.g. hyphen), the length of the slug, and a receipt/evidence payload confirming the paid response was processed.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "tool": "slugify",
  "input": {
   "text": "x402 Seller Growth Tools"
  },
  "route": "/v1/tools/slugify",
  "result": {
   "slug": "slug_example",
   "length": 1,
   "delimiter": "delimiter_example"
  },
  "project": "x402-utility-tools",
  "deterministic": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-utility-tools-slugify-6d2404f4/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)