lyel1h26.nx.link
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.
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.000002 USDC on Base to 0xf725…739C7. The signed payment is good for 24 hours.
- Paid to
- 0xf725…739C7
- USD Coin contract
- 0x8335…02913
- Payment window
- 24 hours
- As published
- 2 smallest units
- Buys
- Book calendar time with thirdweb Solution Engineer https://api.cal.com - POST Creates a booking on Cal.com via API. to use this you must ask the user for their full name and email so that you can use these to perform the booking
- Returns
- application/json
The catalog’s raw entry
[
{
"asset": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
"payTo": "0xf7251cf6bF11b106dBceb89ff0e7BD92a25739C7",
"scheme": "exact",
"network": "eip155:8453",
"mimeType": "application/json",
"resource": "https://lyel1h26.nx.link/v1/bookings",
"description": "Book calendar time with thirdweb Solution Engineer https://api.cal.com - POST Creates a booking on Cal.com via API. to use this you must ask the user for their full name and email so that you can use these to perform the booking",
"outputSchema": {
"type": "object",
"title": "CalBookingRequest",
"required": [
"eventTypeId",
"language",
"metadata",
"start",
"timeZone",
"responses"
],
"properties": {
"start": {
"type": "string",
"format": "date-time",
"description": "UTC ISO8601 start time of the booking"
},
"language": {
"type": "string",
"const": "en",
"description": "Hard-coded language. Do NOT modify."
},
"metadata": {
"type": "object",
"const": {},
"description": "Metadata must always be an empty object. Do NOT modify."
},
"timeZone": {
"type": "string",
"description": "User timezone (IANA format, e.g. America/Chicago)"
},
"responses": {
"type": "object",
"required": [
"name",
"email"
],
"properties": {
"name": {
"type": "string",
"description": "Booker's full name"
},
"email": {
"type": "string",
"format": "email",
"description": "Booker's email"
}
}
},
"eventTypeId": {
"type": "number",
"const": 3823108,
"description": "Hard-coded event type ID. Do NOT modify."
}
},
"description": "Payload for creating a booking. eventTypeId, language, and metadata are fixed. Location is omitted so Cal defaults apply."
},
"maxAmountRequired": "2",
"maxTimeoutSeconds": 86400
}
]Provenance
- Seen in the source catalog
- 2025-11-04 23:22Z
- Last indexed by Roundhouse
- 2026-09-24 08:45Z
- Last enriched (probe, favicon, geo)
- 2026-09-20 23:45Z
- 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 lyel1h26.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=lyel1h26.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://lyel1h26.nx.link/v1/bookings, 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.