# ONE Engine URL Normalize

> ONE Engine URL Normalize is a paid API for AI agents from one-search.one-engine.workers.dev, paid per call via x402, $0.0012/call, status unknown (last checked 2026-10-02).

Parses and normalizes an HTTP/HTTPS URL into structured components like scheme, host, path, query, and fragment

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v1/url/normalize?utm_source=zero.xyz
- Price: $0.0012/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/one-engine-url-normalize-180279ea
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_i-uAOXM4A-dKr3b8LdXDb

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 one-engine-url-normalize-180279ea -d '<json body>'
```

Example prompt: Can you parse this URL into its structured components — scheme, host, path, and query params — and sort the query parameters while stripping the fragment? The URL is https://example.com/search?z=3&a=1#section2

## When to prefer this

Use this endpoint when you need to reliably decompose, clean, or canonicalize a URL for comparison, storage, or downstream processing — especially in agent pipelines that deal with web crawling, link deduplication, or URL normalization at low cost ($0.0012/call via x402). Prefer this over custom regex parsing when you need structured output with optional query sorting and fragment stripping.

## Known failure modes

- Invalid or malformed URL returns an error — non-HTTP/HTTPS protocols (e.g. ftp://, mailto:) are likely rejected
- Empty or missing url field returns a validation error
- Relative URLs without a scheme may fail to parse
- Network timeout on the workers.dev edge function

## How this service works

Parse and normalize an HTTP/HTTPS URL into agent-ready structured components

## Output

A structured JSON object containing the parsed URL components including scheme, host, path, query parameters (optionally sorted), and fragment (optionally stripped), plus the fully normalized URL string ready for agent use.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "description": "HTTP or HTTPS URL"
  },
  "sort_query": {
   "type": "boolean",
   "description": "Sort query parameters. Defaults to false."
  },
  "strip_fragment": {
   "type": "boolean",
   "description": "Remove URL fragment. Defaults to false."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/one-engine-url-normalize-180279ea/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from one-search.one-engine.workers.dev](https://www.zero.xyz/host/one-search.one-engine.workers.dev/llms.txt)