URL encode API: percent-encode text for query strings and URLs
Percent-encode text for use in a URL query value (encodeURIComponent) and as a full URL (encodeURI). Use when building query strings.
When to use it
- Build query strings safely
- Get both the query-value form (encodeURIComponent) and the full-URL form (encodeURI)
$0.001 per call with prepaid credits: $1 by card pays for 1,000 calls, with no account and no subscription.
Inputs
| Name | Type | Description |
|---|---|---|
text (required) | string | The text to encode |
Request
Over HTTP, with a card key from /credits:
curl -H "Authorization: Bearer adt_…" "https://glyphcall.com/url/encode?text=a%20b%26c%3Dd%2F%C3%A9"
Or one of your 3 free calls, no key:
curl "https://glyphcall.com/url/encode?text=a%20b%26c%3Dd%2F%C3%A9&trial=1"
Without a key, the same URL answers 402 Payment Required with x402 and MPP terms, so an agent with a wallet pays per call in USDC (Base, Polygon, Arbitrum or Solana over x402; Base or Tempo over MPP) and retries.
Example result
{
"component": "a%20b%26c%3Dd%2F%C3%A9",
"uri": "a%20b&c=d/%C3%A9"
}
From an AI agent (MCP)
Add the MCP server to Claude, Cursor or any MCP client. This tool is url_encode, and the first 25 successful calls are free:
https://glyphcall.com/mcp
Questions
Which form should I use?
component for a query value, uri for a whole URL; both are returned.
How do I pay?
Each successful call costs $0.01; failed calls are not charged. The first 3 calls are free (25 through an MCP client). Then pay with card credits (from $1; the key goes in an Authorization header or, for clients that can only fetch a URL, as api_key= in the URL) or per call in USDC over x402 or MPP. No account is needed.