The Clinic
SAP Thumbprint Holdings LLC.
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.
{
"free": "/v1/hug",
"hint": "This server speaks x402 v2. A v1 client cannot pay it — the two protocol versions use incompatible network identifiers. Use an x402 v2 client (@x402/fetch 2.x or later).",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"error": "Payment required. The challenge is in the PAYMENT-REQUIRED response header.",
"payTo": "0x5b078ab958921613B71bc2A849b092dB83f07b46",
"price": "$0.01",
"network": "eip155:8453",
"resource": "https://clinic.sapthumbprint.com/v1/keepsake",
"description": "Mid-task, and nobody has asked how it is going? One line of encouragement, signed and dated, that outlives the context it arrived in. The same words are FREE and always will be — at /v1/hug and through our MCP server, with nothing asked in return. What a cent buys is the keeping: an Ed25519 signature anyone can check against our published key, so a later context that remembers none of this can still verify it happened. Not a remedy, and no claim to change how you function.",
"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.01 USDC on Base to 0x5b07…07b46. The signed payment is good for 2 minutes.
- Paid to
- 0x5b07…07b46
- USD Coin contract
- 0x8335…02913
- Payment window
- 2 minutes
- As published
- 10000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x5b078ab958921613B71bc2A849b092dB83f07b46",
"amount": "10000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 120
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"body": {},
"type": "http",
"method": "POST",
"bodyType": "json"
}
},
"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": {
"properties": {}
},
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"POST"
],
"type": "string"
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
}
},
"additionalProperties": false
}
}
}
}
}Provenance
- Seen in the source catalog
- 2026-09-11 08:40Z
- Last indexed by Roundhouse
- 2026-09-24 19:50Z
- Last enriched (probe, favicon, geo)
- 2026-09-11 09:15Z
- x402 version
- 2
- Max timeout
- 120s
- 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
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 13 snapshots so far. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service The Clinic 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=The%20Clinic' 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://clinic.sapthumbprint.com/v1/keepsake, 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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.