07hsvih4.nx.link
No description published for this endpoint.
OtherLiveeip155:8453Exactvia facilitator:thirdweb
Activity
—
Nothing indexed for this service or its provider yet. Not a claim that it is unused — only that we hold no record.
$0.00055
Verified settled volume
5 settlements proven x402 by their on-chain EIP-3009 marker.
$0.00
Listed price
As published in the catalog. Always read the live 402 before paying.
—
Calls · 30d
Upstream's own call count for this endpoint, not ours.
—
Unique payers · 30d
Never called
—
Upstream on-chain volume
Reported by the source catalog.
Paid to
0xc801C038CcD190d9E915FAE1d69530eB6A889972The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fcd6edb6e08f4c7c32d4f71b54bda02913
Provider
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.
0.000110USDC≈ $ USD
on Base · exact scheme
That figure is in the token’s smallest units. Roundhouse does not hold this contract’s decimals, so it is shown as published rather than converted.
- Paid to
- 0xc801…89972
- USD Coin contract
- 0x8335…02913
- Payment window
- 24 hours
- Buys
- x402 https://api.thirdweb.com - POST Create Payment
- Returns
- application/json
The catalog’s raw entry
[
{
"asset": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
"payTo": "0xc801C038CcD190d9E915FAE1d69530eB6A889972",
"scheme": "exact",
"network": "eip155:8453",
"mimeType": "application/json",
"resource": "https://07hsvih4.nx.link/v1/payments",
"description": "x402 https://api.thirdweb.com - POST Create Payment",
"outputSchema": {
"responses": {
"200": {
"content": {
"application/json": {
"schema": {
"type": "object",
"title": "Create Payment Response",
"required": [
"result"
],
"properties": {
"result": {
"type": "object",
"required": [
"id",
"link"
],
"properties": {
"id": {
"type": "string",
"description": "The payment ID"
},
"link": {
"type": "string",
"description": "The link to purchase the product"
}
}
}
},
"description": "Successful payment creation response containing the payment ID and link to purchase the product"
}
}
},
"description": "Payment created successfully. Returns the ID and link to complete the payment."
},
"400": {
"description": "Invalid request parameters."
},
"401": {
"description": "Authentication required. For backend usage, include `x-secret-key` header. For frontend usage, include `x-client-id` + `Authorization: Bearer <jwt>` headers."
},
"500": {
"description": "Internal server error. This may occur due to network connectivity issues, wallet creation failures, or transaction execution failures."
}
},
"requestBody": {
"content": {
"application/json": {
"schema": {
"type": "object",
"title": "Create Product Request",
"examples": [
{
"name": "Course",
"token": {
"amount": "100",
"address": "0xaf88d065e77c8cC2239327C5EDb3A432268e5831",
"chainId": 42161
},
"imageUrl": "https://example.com/course.png",
"recipient": "0xEfc38EF8C09535b25e364b6d1a7C406D3972f2A9",
"description": "The complete javascript course"
}
],
"required": [
"name",
"description",
"token",
"recipient"
],
"properties": {
"name": {
"type": "string",
"description": "The name of the product"
},
"token": {
"type": "object",
"required": [
"address",
"chainId",
"amount"
],
"properties": {
"amount": {
"type": "string",
"description": "The amount of the token to purchase in wei."
},
"address": {
"type": "string",
"description": "The token address to purchase (use 0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE for native token)"
},
"chainId": {
"type": "integer",
"description": "The blockchain network where the token is located",
"exclusiveMinimum": 0
}
},
"description": "The token to purchase"
},
"imageUrl": {
"type": "string",
"description": "The URL of the product image"
},
"recipient": {
"type": "string",
"description": "The wallet address or ENS name that will receive the payment for the product"
},
"description": {
"type": "string",
"description": "The description of the product"
},
"purchaseData": {
"description": "App specific purchase data for this payment"
}
},
"description": "Request to create a product to be purchased. Users can purchase the product via hosted UI (link is returned), a transaction execution referencing the product ID, or embedded widgets with the product ID."
}
}
}
}
},
"maxAmountRequired": "0.000110",
"maxTimeoutSeconds": 86400
}
]Provenance
- Seen in the source catalog
- 2025-11-29 19:36Z
- Last indexed by Roundhouse
- 2026-09-24 20:15Z
- Last enriched (probe, favicon, geo)
- 2026-09-14 17:46Z
- x402 version
- 1
- Max timeout
- 86400s
- Liveness probe
- HTTP 404
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
Nothing indexed for this service or its provider yet. Not a claim that it is unused — only that we hold no record. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service 07hsvih4.nx.link 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=07hsvih4.nx.link' 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://07hsvih4.nx.link/v1/payments, 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.