Back to Browse
Delx URL Parts
x402
Delx URL Parts is a paid API for AI agents from api.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-13).
Splits a URL into its constituent parts: scheme, netloc, path, query, and fragment — no network access required.
Price / call$0.001
Success—
StatusUnknown
How this service works
Split a URL into scheme/netloc/path/query/fragment. Call when you inspect agent-held URLs without network access. Returns URL parts and ok for $0.001 USDC via x402 on Base. No network, no keys, no retention; first-party local JSON only. Results are advisory; the caller owns budgets, auth, and production controls.
Output
Returns a JSON object with the parsed URL components: scheme (e.g. 'https'), netloc (e.g. 'example.com'), path (e.g. '/search'), query (e.g. 'q=hello'), fragment (e.g. 'results'), and an 'ok' boolean indicating successful parsing. No external network calls are made.
Example use cases
Extracting query parameters from a URL
“I have this URL — https://shop.example.com/products?category=shoes&color=red — can you break it apart so I can see the query string separately from the path?”
Identifying the host of a stored URL
“I've got a bunch of URLs stored in my notes and I need to know just the netloc (domain) part of this one: https://api.partner.io/v2/data/export?token=abc123”
Debugging a URL fragment in an agent workflow
“Can you parse this URL and tell me what the fragment identifier is? The URL is https://docs.myapp.com/guide/setup#installation-step-3”
Technical details
Endpoint
POSThttps://api.delx.ai/api/v1/x402/url-partsWhen to prefer
Choose this endpoint when you need to decompose a URL into its components without making any network request or requiring API keys. It is ideal for agent workflows that hold URLs as strings and need to route, filter, or inspect them based on their structure. Prefer it over regex-based parsing for reliability, and over full page-fetch endpoints when no content retrieval is needed.
Side effects
- Malformed or empty URL input may result in empty component fields or ok=false
- Non-HTTP schemes (e.g. ftp://, mailto:) may parse with limited field population
- Payment failure via x402 protocol results in 402 response and no result
- Missing 'url' field in request body returns a validation error
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| url | string | Input field: url. |
Output
Schema · Response
{
"type": "json",
"example": {
"ok": true,
"path": "/x",
"query": "y=1",
"netloc": "api.delx.ai",
"schema": "delx/util-url-parts/v1",
"scheme": "https",
"fragment": "z"
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"