Discover / url.openverbs.com

Query string parse / build

■ Challenge detected

Two directions over query strings. action='parse' decodes a query string (with or without a leading '?') into an object, collapsing repeated keys into arrays. action='build' encodes a params object into a query string, expanding array values into repeated keys; set sort=true to order keys alphabetically.

Listed price
$0.002
Challenge detected
9 of the last 9 checks
Median response
192 ms
Last checked
16 Oct, 18:49 UTC
In our index since
26 Sept 2026

Endpoint

curl -i https://url.openverbs.com/v1/query
# 402 Payment Required: pay with an x402 client (USDC on Base),
# then send the same request again with the payment attached.
4 listed endpoints · on x402 Bazaar

Checks and payment terms on this page refer to the endpoint above. Other listed endpoints have not been checked individually.

Base URLhttps://url.openverbs.com/v1

  • POST/parse$0.002Parse an absolute URL into its WHATWG components: protocol/scheme, credentials, host/hostname/port, origin, pathname (plus path segments), search (plus a decoded query object) and hash. A string that is not a valid absolute URL is rejected as a clean 400.
  • POST/query$0.002Two directions over query strings. action='parse' decodes a query string (with or without a leading '?') into an object, collapsing repeated keys into arrays. action='build' encodes a params object into a query string, expanding array values into repeated keys; set sort=true to order keys alphabetically.
  • POST/normalize$0.002Canonicalize a URL: WHATWG parsing already lowercases the host, resolves dot-segments and drops default ports; on top of that, query parameters are sorted by default and you can optionally drop the fragment or a trailing slash. Returns the normalized URL and whether it changed.
  • POST/resolve$0.002Resolve a relative or absolute reference against a base URL, following RFC 3986 reference resolution (e.g. base 'https://a.com/x/y' + ref '../z' → 'https://a.com/z'). The base must itself be a valid absolute URL, else a clean 400.

A dash means the listing gives no price or method. Copy buttons copy the full URL.

Showing 4 of 4 listed endpoints.

Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/url.openverbs.com

Recent checks

2 Oct 2026One bar per check, showing up to 20 recent checks. Coloured bars show relative response time, with a minimum visible height; full-height grey bars mean no challenge was detected. “Challenge detected” means HTTP 402 or another detected payment-challenge signal.16 Oct 2026
All 9 checks
When (UTC)ResultHTTPResponse
16 Oct, 18:49 UTCChallenge detected402182ms
15 Oct, 11:37 UTCChallenge detected402175ms
14 Oct, 00:19 UTCChallenge detected402192ms
12 Oct, 00:34 UTCChallenge detected402238ms
10 Oct, 10:04 UTCChallenge detected402300ms
9 Oct, 03:33 UTCChallenge detected402192ms
8 Oct, 00:44 UTCChallenge detected402163ms
6 Oct, 21:30 UTCChallenge detected402466ms
2 Oct, 17:03 UTCChallenge detected402173ms

Questions

Did our last probe detect a payment challenge?

At our last probe on 16 Oct, 18:49 UTC, it returned HTTP 402 or another detected payment-challenge signal. This check did not test payment, delivery or compatibility with the Superstables client.

What price is recorded for Query string parse / build?

Its listed price is $0.002.

What payment terms does Query string parse / build advertise?

The listing advertises x402, Base and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.

Where is Query string parse / build listed?

In x402 Bazaar. Superstables first indexed it on 26 Sept 2026.

Something wrong on this page? Tell us.