Back to Browse
Location Header Resolve
x402
Location Header Resolve 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).
Resolves a relative Location header value against a base URL to produce a normalized absolute URL with pass/advisory validation status.
Price / call$0.001
Success—
StatusUnknown
How this service works
Location Header Resolve: Location Header Resolve resolves a relative Location value against a caller-supplied base URL from bounded caller-supplied values without an external provider. Call Location Header Resolve before accepting, caching, redirecting, or retrying a caller-supplied web response. Returns normalized web evidence, the computed finding, and an explicit pass or advisory status for Location Header Resolve as versioned deterministic JSON. Price: $0.001 USDC via x402 on Base. First-pa…
Output
Returns a versioned deterministic JSON object containing: the normalized absolute URL (computed by resolving the relative Location value against the base URL), the computed finding describing the resolution result, and an explicit pass or advisory status indicating whether the resolved URL is acceptable.
Example use cases
Redirect safety check before following
“Before my agent follows this redirect, resolve the Location header value '../auth/callback' against the base URL 'https://app.myservice.com/login' and tell me if the resulting URL is safe to accept.”
Cache key normalization for redirect responses
“I need to normalize the Location header '/v2/users/profile' against 'https://api.example.com/v1/login' into a canonical absolute URL before I store it in my redirect cache.”
Retry logic URL resolution
“My HTTP client got a 302 with Location '/retry-endpoint' from 'https://payments.provider.io/submit' — can you compute the full absolute URL I should retry against?”
Technical details
Endpoint
POSThttps://api.delx.ai/api/v1/x402/location-header-resolveWhen to prefer
Choose this endpoint when you need a deterministic, stateless, in-memory resolution of a relative HTTP Location header against a known base URL — especially before accepting, caching, retrying, or following a redirect. Prefer this over manual URL string concatenation when you need normalized output with an explicit pass/advisory safety signal and versioned JSON evidence for audit trails.
Side effects
- Invalid or malformed base_url causing resolution failure
- Relative Location value that cannot be resolved against the given base
- base_url or location exceeding 8192 character limit
- Missing required input fields returning validation error
- Location value that is already absolute and conflicts with base URL scheme/host
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| base_url | string | Base URL supplied to Location Header Resolve; used only for this bounded calculation and processed in memory without retention. |
| location | string | Location supplied to Location Header Resolve; used only for this bounded calculation and processed in memory without retention. |
Output
Schema · Response
{
"type": "json",
"example": {
"result": {
"resolved_url": "https://example.com/login"
},
"schema": "delx/util-location-header-resolve/v1",
"status": "pass",
"evidence": {
"retained": false,
"input_sha256": "b195fccec2384b3775b4cdbcc370ff5f1189afe143f8e39e6286a1cbbe96c94a",
"external_calls": 0
},
"operation": "web_reliability:location_header_resolve"
}
}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"