# Avedaris URL Parser

> Avedaris URL Parser is a paid API for AI agents from api.avedaris.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Parses an HTTP(S) URL into normalized, structured components such as scheme, host, path, query parameters, and fragment.

## Facts

- Endpoint: POST https://api.avedaris.com/v1/paid/url-parse
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/avedaris-url-parser-e2f51738
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__RDTfJwqnwvips-E8Ug9v

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 avedaris-url-parser-e2f51738 -d '<json body>'
```

Example prompt: Can you parse the URL 'https://shop.example.com/products?category=shoes&sort=price#results' into its structured components — scheme, host, path, query params, and fragment?

## When to prefer this

Use this endpoint when you need a reliable, deterministic, server-side parse of an HTTP(S) URL into fully normalized structured components — especially when client-side parsing is unavailable, unreliable, or when you need consistent normalization across different URL formats. Prefer it over regex-based or ad-hoc parsing when accuracy and normalization matter.

## Known failure modes

- Invalid or malformed URL returns a parse error or diagnostics
- Non-HTTP/HTTPS schemes (e.g. ftp://, mailto:) may be rejected or unsupported
- Empty or missing URL field returns a validation error
- URL exceeding 8192 characters is rejected
- Payment failure via x402 protocol blocks the request

## How this service works

AveDaris is the economic coordination layer for autonomous software: discover, route, evaluate, procure, verify, and learn across agent services.

## Output

A structured object containing the normalized components of the input URL, including scheme (protocol), host (domain), port, path, query string broken into key-value pairs, and fragment identifier. Values are normalized and consistently formatted.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "maxLength": 8192,
   "minLength": 1
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "hash": "#top",
   "port": "",
   "query": [
    [
     "x",
     "1"
    ]
   ],
   "hostname": "example.com",
   "pathname": "/a",
   "protocol": "https:"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/avedaris-url-parser-e2f51738/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.avedaris.com](https://www.zero.xyz/host/api.avedaris.com/llms.txt)