zkbcy7ja.nx.link
No description published for this endpoint.
DataLiveeip155: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 Sign Typed Data
- 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/sign-typed-data",
"description": "thirdweb API https://api.thirdweb.com/ - POST Sign Typed Data",
"outputSchema": {
"responses": {
"200": {
"content": {
"application/json": {
"schema": {
"type": "object",
"required": [
"result"
],
"properties": {
"result": {
"type": "object",
"required": [
"signature"
],
"properties": {
"signature": {
"type": "string",
"description": "The cryptographic signature in hexadecimal format. This can be used for verification and authentication purposes."
}
}
}
}
}
}
},
"description": "Typed data signed successfully. Returns the EIP-712 compliant signature that can be used for on-chain verification."
},
"400": {
"description": "Invalid request parameters. This occurs when the typed data structure is malformed, domain parameters are incorrect, or wallet address format is invalid."
},
"401": {
"description": "Authentication required. The request must include valid `x-wallet-access-token` headers for accessing the wallet, as well as a x-client-id (frontend) or x-secret-key (backend) for project authentication."
},
"500": {
"description": "Internal server error. This may occur due to wallet connectivity issues, signing service unavailability, or unexpected server errors."
}
},
"requestBody": {
"content": {
"application/json": {
"schema": {
"type": "object",
"examples": [
{
"from": "0x1234567890123456789012345678901234567890",
"types": {
"MyType": [
{
"name": "name",
"type": "string"
}
]
},
"domain": {
"name": "MyDomain",
"chainId": "1",
"version": "1",
"verifyingContract": "0x1234567890123456789012345678901234567890"
},
"chainId": 1,
"message": {
"name": "foo"
},
"primaryType": "MyType"
}
],
"required": [
"from",
"chainId",
"domain",
"message",
"primaryType",
"types"
],
"properties": {
"from": {
"type": "string",
"description": "The wallet address or ENS name that will sign the typed data."
},
"types": {
"type": "object",
"description": "Type definitions for the structured data, following EIP-712 specifications.",
"additionalProperties": {
"type": "array",
"items": {
"type": "object",
"required": [
"name",
"type"
],
"properties": {
"name": {
"type": "string",
"description": "The field name"
},
"type": {
"type": "string",
"description": "The Solidity type (e.g., 'address', 'uint256')"
}
}
}
}
},
"domain": {
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "The domain name (e.g., token name)"
},
"salt": {
"type": "string",
"description": "Optional salt for additional entropy"
},
"chainId": {
"type": "string",
"description": "Chain ID as string for domain separation"
},
"version": {
"type": "string",
"description": "Domain version for signature compatibility"
},
"verifyingContract": {
"type": "string",
"description": "The contract address that will verify this signature"
}
},
"description": "EIP-712 domain separator containing contract and chain information for signature verification."
},
"chainId": {
"type": "integer",
"description": "The blockchain network identifier for EIP-712 domain separation.",
"exclusiveMinimum": 0
},
"message": {
"type": "object",
"description": "The structured data to be signed, matching the defined types schema.",
"additionalProperties": {}
},
"primaryType": {
"type": "string",
"description": "The primary type name from the types object that defines the main structure being signed."
}
},
"description": "Request body for signing typed data"
}
}
}
}
},
"maxAmountRequired": "0.100033",
"maxTimeoutSeconds": 86400
}
]Provenance
- Seen in the source catalog
- 2026-01-27 00:53Z
- Last indexed by Roundhouse
- 2026-09-24 07: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/sign-typed-data, 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.