api.pay-forge.online
No description published for this endpoint.
The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fcd6edb6e08f4c7c32d4f71b54bda02913
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.
Live 402 challenge
Captured by the enrichment pass, not read just now. Prices can change — always read the 402 the endpoint answers with.
{
"error": "Payment required",
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0xd8dd9fc8c143207ddbe84e1e9237f11a69814cb5",
"amount": "4000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
],
"resource": {
"url": "https://api.pay-forge.online/v1/normalize-url",
"tags": [
"normalize URL",
"URL normalization",
"tracking parameter removal",
"link deduplication",
"URL hashing"
],
"mimeType": "application/json",
"description": "Normalize URL strings for link deduplication and stable hashing without network access. Deterministic URL normalization using Python urllib.parse: strip surrounding whitespace, require parsed http/https scheme and nonempty authority, lowercase scheme and the entire authority (including any userinfo), use / for an empty path, remove the final path-parameter component and fragment. Decode/re-encode query pairs with urllib.parse.parse_qsl/urlencode, preserving order, duplicate keys and blank values; remove keys beginning with utm_, fbclid, gclid or yclid case-insensitively. Does not sort queries, resolve dot segments, remove default ports or validate port numbers/hosts; ports remain in the lowercased authority. Not a fetch, redirect resolver, security validator or universal canonical URL equivalence test. Returns exactly url and sha256 (SHA-256 of its UTF-8 bytes). Non-http(s), missing authority and parser errors return 422. POST application/json with url. Limit: 50000 input Unicode characters per request; for comparison, the lengths of a and b are added. Empty strings are accepted. Extra JSON properties are ignored. Errors after payment verification: 413 for the character limit; 422 for missing/non-string fields or malformed JSON, and for URL parsing errors. Unpaid calls return 402 with a base64 JSON PAYMENT-REQUIRED header before input validation. Handler error responses are not settled. ",
"serviceName": "Machine Shop"
},
"extensions": {
"bazaar": {
"info": {
"input": {
"body": {
"url": " HTTPS://Example.COM:443/a;b?b=2&utm_source=news&a=1&a=&FBCLID=x#section "
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"url": "https://example.com:443/a?b=2&a=1&a=",
"sha256": "989aed231bfce2ac8018bbf402486009ceb15ff1a46cf53d8b0e300c53d4c9ad"
}
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method",
"bodyType",
"body"
],
"properties": {
"body": {
"type": "object",
"title": "UrlIn",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"title": "Url",
"maxLength": 50000,
"description": "Absolute HTTP/HTTPS URL string, at most 50000 characters before trimming. Syntax parsing only; not a URL safety check."
}
}
},
"type": {
"type": "string",
"const": "http"
},
"method": {
"type": "string",
"const": "POST"
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object",
"title": "UrlOut",
"required": [
"url",
"sha256"
],
"properties": {
"url": {
"type": "string",
"title": "Url",
"description": "Normalized URL string. Syntactic transformation only; not fetched or safety-validated."
},
"sha256": {
"type": "string",
"title": "Sha256",
"pattern": "^[0-9a-f]{64}$",
"description": "Lowercase SHA-256 hex digest of the normalized URL encoded as UTF-8."
}
},
"additionalProperties": false
}
}
}
}
}
}
},
"x402Version": 2
}Accepts
The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.
Pay 0.004 USDC on Base to 0xd8dd…14cb5. The signed payment is good for 5 minutes.
- Paid to
- 0xd8dd…14cb5
- USD Coin contract
- 0x8335…02913
- Payment window
- 5 minutes
- As published
- 4000 smallest units
- Returns
- application/json
The catalog’s raw entry
[
{
"asset": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0xd8dd9fc8c143207ddbe84e1e9237f11a69814cb5",
"scheme": "exact",
"network": "eip155:8453",
"mimeType": "application/json",
"resource": "https://api.pay-forge.online/v1/normalize-url",
"description": "",
"maxAmountRequired": "4000",
"maxTimeoutSeconds": 300
}
]Provenance
- Seen in the source catalog
- 2026-10-18 18:57Z
- Last indexed by Roundhouse
- 2026-10-21 12:46Z
- Last enriched (probe, favicon, geo)
- 2026-10-21 14:17Z
- x402 version
- 1
- Max timeout
- 300s
- Liveness probe
- HTTP 402
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service api.pay-forge.online and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=api.pay-forge.online' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://api.pay-forge.online/v1/normalize-url, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.