# Delx Commerce URL Origin Extractor

> Delx Commerce URL Origin Extractor 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-01).

Parses a URL string and returns its normalized origin components (scheme, host, port, and full origin string)

## Facts

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

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-origin-extractor-0f796824 -d '<json body>'
```

Example prompt: Can you extract the origin — scheme, host, and port — from the URL https://api.example.com:8080/some/path?query=1 and tell me what the normalized origin string is?

## When to prefer this

Use this endpoint when you need a lightweight, pay-per-call, no-signup utility to reliably parse and normalize a URL into its canonical origin components. Prefer it over rolling your own URL parsing logic when you need a verifiable, deterministic result with micropayment billing via USDC on Base or Solana.

## Known failure modes

- Invalid or malformed URL input returns an error or ok:false
- Missing 'url' field in request body causes a 400-level error
- Non-HTTP/HTTPS schemes may not be supported or return unexpected results
- Network or service downtime returns a 5xx error

## How this service works

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

## Output

Returns a JSON object with a boolean 'ok' field indicating success, the 'host' (e.g. api.delx.ai), 'port' (integer), 'origin' (full origin string like https://api.delx.ai:443), 'scheme' (e.g. https), and a 'schema' identifier string referencing the response format version.

## 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,
  "host": "api.delx.ai",
  "port": 443,
  "origin": "https://api.delx.ai:443",
  "schema": "delx/util-url-origin/v1",
  "scheme": "https"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-url-origin-extractor-0f796824/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)