zkbcy7ja.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.
—
Verified settled volume
0 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
0xE1F27E03BDBAd7a70055B52Af30B2dB9537F43FdThe 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.100033USDC≈ $ 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
- 0xE1F2…F43Fd
- USD Coin contract
- 0x8335…02913
- Payment window
- 24 hours
- Buys
- thirdweb API https://api.thirdweb.com/ - POST Send Tokens
- Returns
- application/json
The catalog’s raw entry
[
{
"asset": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
"payTo": "0xE1F27E03BDBAd7a70055B52Af30B2dB9537F43Fd",
"scheme": "exact",
"network": "eip155:8453",
"mimeType": "application/json",
"resource": "https://zkbcy7ja.nx.link/v1/wallets/send",
"description": "thirdweb API https://api.thirdweb.com/ - POST Send Tokens",
"outputSchema": {
"responses": {
"200": {
"content": {
"application/json": {
"schema": {
"type": "object",
"required": [
"result"
],
"properties": {
"result": {
"type": "object",
"required": [
"transactionIds"
],
"properties": {
"transactionIds": {
"type": "array",
"items": {
"type": "string"
},
"description": "Array of transaction IDs for the submitted transfers. One ID per recipient."
}
}
}
}
}
}
},
"description": "Tokens sent successfully. Returns transaction IDs for tracking and monitoring."
},
"400": {
"description": "Invalid request parameters. This occurs when token parameters are malformed, insufficient balance, invalid contract data, or unsupported token type."
},
"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 blockchain connectivity issues, gas estimation failures, contract execution errors, or unexpected server errors."
}
},
"requestBody": {
"content": {
"application/json": {
"schema": {
"type": "object",
"examples": [
{
"from": "0x1234567890123456789012345678901234567890",
"chainId": 1,
"recipients": [
{
"address": "0xabcdefabcdefabcdefabcdefabcdefabcdefabcd",
"quantity": "1000000000000000000"
},
{
"address": "0x1111111111111111111111111111111111111111",
"quantity": "500000000000000000"
}
]
}
],
"required": [
"chainId",
"recipients"
],
"properties": {
"from": {
"type": "string",
"description": "The wallet address or ENS name that will send the tokens. If omitted, the project wallet will be used if available."
},
"chainId": {
"type": "integer",
"examples": [
1,
8453,
137,
56,
43114,
42161,
10
],
"description": "The blockchain network identifier where the transfer will be executed.",
"exclusiveMinimum": 0
},
"tokenId": {
"type": "string",
"description": "The token ID for NFT transfers (ERC721/ERC1155). Required for NFT transfers."
},
"recipients": {
"type": "array",
"items": {
"type": "object",
"required": [
"address",
"quantity"
],
"properties": {
"address": {
"type": "string",
"description": "The recipient wallet address or ENS name"
},
"quantity": {
"type": "string",
"description": "The amount to send. For native tokens and ERC20: amount in wei/smallest unit. For ERC721: should be '1'. For ERC1155: the number of tokens to transfer."
}
}
},
"maxItems": 100,
"minItems": 1,
"description": "Array of recipients and quantities. Maximum 100 recipients per request."
},
"tokenAddress": {
"type": "string",
"description": "The token contract address. Omit for native token (ETH, MATIC, etc.) transfers."
}
},
"description": "Request body for sending tokens to multiple recipients. Supports native tokens, ERC20, ERC721, and ERC1155 transfers based on the provided parameters."
}
}
}
}
},
"maxAmountRequired": "0.100033",
"maxTimeoutSeconds": 86400
}
]Provenance
- Seen in the source catalog
- 2026-01-27 00:53Z
- Last indexed by Roundhouse
- 2026-09-24 09:45Z
- Last enriched (probe, favicon, geo)
- 2026-09-21 00:15Z
- 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 zkbcy7ja.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=zkbcy7ja.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://zkbcy7ja.nx.link/v1/wallets/send, 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.