# OpenTools URL Parse

> OpenTools URL Parse is a paid API for AI agents from chargers-borders-cedar-fig.trycloudflare.com, paid per call via x402, price unknown, status unknown (last checked 2026-10-23).

Parses and decomposes a URL string into its constituent components via an HTTP POST request

## Facts

- Endpoint: POST https://chargers-borders-cedar-fig.trycloudflare.com/tools/url-parse?utm_source=zero.xyz
- Price: price unknown
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/opentools-url-parse-7afbce4a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PX1nce0TdwNynexxOlFIg

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 opentools-url-parse-7afbce4a -d '<json body>'
```

Example prompt: Can you parse this URL for me — https://example.com/products?category=shoes&size=10#reviews — and break it down into its protocol, host, path, query parameters, and fragment?

## When to prefer this

Choose this endpoint when you need a simple, serverless utility to parse and decompose URLs into structured components without standing up your own parser. It is best suited for lightweight workflows where an agent needs to extract query parameters, hostnames, or path segments from raw URL strings on the fly.

## Known failure modes

- Malformed or non-URL input may return a parsing error or empty fields
- Missing required 'input' object causes schema validation failure
- Invalid HTTP method (not POST/PUT/PATCH) returns a method not allowed error
- Empty or null URL string may return an error or all-empty component fields
- Cloudflare tunnel downtime may cause connection errors or timeouts

## How this service works

opentools utility endpoint

## Output

Returns the parsed components of the submitted URL, broken down into structured fields such as protocol/scheme, host, pathname, query parameters as key-value pairs, port, and fragment/hash identifier.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/opentools-url-parse-7afbce4a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from chargers-borders-cedar-fig.trycloudflare.com](https://www.zero.xyz/host/chargers-borders-cedar-fig.trycloudflare.com/llms.txt)