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
0xE1F27E03BDBAd7a70055B52Af30B2dB9537F43Fd

The 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.

USD Coin contract
0x8335…02913
Payment window
24 hours
Buys
thirdweb API https://api.thirdweb.com/ - POST Read Contract
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/contracts/read",
    "description": "thirdweb API https://api.thirdweb.com/ - POST Read Contract",
    "outputSchema": {
      "responses": {
        "200": {
          "content": {
            "application/json": {
              "schema": {
                "type": "object",
                "required": [
                  "result"
                ],
                "properties": {
                  "result": {
                    "type": "array",
                    "items": {
                      "type": "object",
                      "required": [
                        "success"
                      ],
                      "properties": {
                        "data": {
                          "description": "The result of the contract read operation. The type and format depend on the method's return value as defined in the contract ABI."
                        },
                        "error": {
                          "type": "string",
                          "description": "Error message if the contract read operation failed."
                        },
                        "success": {
                          "type": "boolean",
                          "description": "Indicates whether the contract read operation was successful."
                        }
                      }
                    },
                    "description": "Array of results corresponding to each contract read call. Results are returned in the same order as the input calls."
                  }
                }
              }
            }
          },
          "description": "Contract read operations completed successfully. Returns an array of results corresponding to each input call, including both successful and failed operations."
        },
        "400": {
          "description": "Invalid request parameters. This occurs when the chainId is not supported, contract addresses are invalid, function signatures are malformed, or the calls array is empty."
        },
        "401": {
          "description": "Authentication required. The request must include a valid `x-client-id` header for frontend usage or `x-secret-key` for backend usage."
        },
        "500": {
          "description": "Internal server error. This may occur due to engine connectivity issues, RPC node unavailability, or unexpected server errors."
        }
      },
      "requestBody": {
        "content": {
          "application/json": {
            "schema": {
              "type": "object",
              "example": {
                "calls": [
                  {
                    "method": "function name() view returns (string)",
                    "contractAddress": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
                  },
                  {
                    "method": "function totalSupply() returns (uint256)",
                    "contractAddress": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
                  },
                  {
                    "method": "function balanceOf(address) returns (uint256)",
                    "params": [
                      "0x742d35Cc6634C0532925a3b8D43C67B8c8B3E9C6"
                    ],
                    "contractAddress": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
                  }
                ],
                "chainId": 8453
              },
              "required": [
                "calls",
                "chainId"
              ],
              "properties": {
                "calls": {
                  "type": "array",
                  "items": {
                    "type": "object",
                    "required": [
                      "contractAddress",
                      "method"
                    ],
                    "properties": {
                      "value": {
                        "type": "string",
                        "description": "Amount of native token to send with the transaction in wei. Required for payable methods."
                      },
                      "method": {
                        "type": "string",
                        "pattern": "^function\\s+\\w+",
                        "description": "The contract function signature to call (e.g., 'function approve(address spender, uint256 amount)' or `function balanceOf(address)`). Must start with 'function' followed by the function name and parameters as defined in the contract ABI. For functions returning arrays of structs, use positional types only in the return declaration (e.g., `returns ((uint256, address, bool)[])` instead of `returns ((uint256 id, address owner, bool active)[] items)`)."
                      },
                      "params": {
                        "type": "array",
                        "items": {},
                        "description": "Array of parameters to pass to the contract method, in the correct order and format."
                      },
                      "contractAddress": {
                        "type": "string",
                        "description": "The smart contract address or ENS name."
                      }
                    }
                  },
                  "minItems": 1,
                  "description": "Array of contract method calls to execute. Each call specifies a contract address, method signature, and optional parameters."
                },
                "chainId": {
                  "type": "integer",
                  "examples": [
                    1,
                    8453,
                    137,
                    56,
                    43114,
                    42161,
                    10
                  ],
                  "description": "The blockchain network identifier. Common values include: 1 (Ethereum), 8453 (Base), 137 (Polygon), 56 (BSC), 43114 (Avalanche), 42161 (Arbitrum), 10 (Optimism).",
                  "exclusiveMinimum": 0
                }
              }
            }
          }
        }
      }
    },
    "maxAmountRequired": "0.100033",
    "maxTimeoutSeconds": 86400
  }
]

Provenance

Seen in the source catalog
2026-01-27 00:53Z
Last indexed by Roundhouse
2026-09-24 10:45Z
Last enriched (probe, favicon, geo)
2026-09-21 00:15Z
x402 version
1
Max timeout
86400s
Liveness probe
HTTP 404
Report

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.

Open skill.md
Show 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/contracts/read, 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.