x402 Utils
Run a regular expression on a text: every match with its position and capture groups (named too), and the text with a replacement applied. RE2 syntax, which runs in linear time (no lookaround or backreferences).
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.
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.001 USDC on Base to 0xe6f7…3c3f8. The signed payment is good for 5 minutes.
- Paid to
- 0xe6f7…3c3f8
- USD Coin contract
- 0x8335…02913
- Payment window
- 5 minutes
- As published
- 1000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0xe6f7508ab572a4dc9c7486ea017b100d83f3c3f8",
"amount": "1000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"body": {
"text": "from 2026-10 to 2027-01",
"pattern": "(?P<year>\\d{4})-(\\d{2})",
"replacement": "$2/$1"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"count": 2,
"matched": true,
"matches": [
{
"index": 5,
"match": "2026-10",
"named": {
"year": "2026"
},
"groups": [
"2026",
"10"
]
}
],
"replaced": "from 10/2026 to 01/2027"
}
}
},
"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": {
"required": [
"pattern",
"text"
],
"properties": {
"text": {
"type": "string",
"description": "the text (up to 1 MB)"
},
"flags": {
"type": "string",
"description": "any of i (ignore case), m (multiline), s (dot matches newline)"
},
"pattern": {
"type": "string",
"description": "the pattern (up to 2000 characters)"
},
"replacement": {
"type": "string",
"description": "optional replacement, $1 for groups"
}
}
},
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"POST"
],
"type": "string"
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object",
"properties": {
"count": {},
"matched": {},
"matches": {},
"replaced": {}
}
}
}
}
}
}
}
}Provenance
- Seen in the source catalog
- 2026-10-25 01:38Z
- Last indexed by Roundhouse
- 2026-10-26 17:20Z
- Last enriched (probe, favicon, geo)
- —
- x402 version
- 2
- Max timeout
- 300s
- Liveness probe
- Not probed
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 x402 Utils 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=x402%20Utils' 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://qcb7fnxsbd7fbhj4.68r.lambda-web.us-east-1.on.aws/v1/regex, 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.