# Delx Commerce URL Parts Parser

> Delx Commerce URL Parts Parser is a paid API for AI agents from commerce.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-02).

Parses a URL string into its component parts: scheme, netloc, path, query, and fragment

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/url-parts?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-commerce-url-parts-parser-bc4f708d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IrTH_-zGWmB5t9mQ8O9xT

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 delx-commerce-url-parts-parser-bc4f708d -d '<json body>'
```

Example prompt: Can you break down the URL 'https://api.delx.ai/x?y=1#z' into its individual parts like scheme, host, path, query, and fragment?

## When to prefer this

Choose this endpoint when you need a quick, pay-per-result URL decomposition without setting up a library or parsing URLs manually in an agent pipeline. It's ideal for serverless or agent workflows where you need structured URL components on demand for a fraction of a cent per call, with no API key or signup required.

## Known failure modes

- Malformed or empty URL input may return ok:false or an error response
- Missing 'url' field in request body causes a bad request error
- Relative URLs (without scheme) may produce empty scheme/netloc fields
- Extremely long URLs may be rejected or truncated

## How this service works

Pay-per-result APIs for agents. No signup. Exact price. Verifiable delivery. USDC on Base + Solana via x402.

## Output

A JSON object with boolean 'ok' plus string fields: 'scheme' (e.g. 'https'), 'netloc' (e.g. 'api.delx.ai'), 'path' (e.g. '/x'), 'query' (e.g. 'y=1'), and 'fragment' (e.g. 'z'), along with a 'schema' identifier ('delx/util-url-parts/v1').

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "description": "Input field: url."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "path": "/x",
  "query": "y=1",
  "netloc": "api.delx.ai",
  "schema": "delx/util-url-parts/v1",
  "scheme": "https",
  "fragment": "z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-url-parts-parser-bc4f708d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from commerce.delx.ai](https://www.zero.xyz/host/commerce.delx.ai/llms.txt)