Ethereum Nfts
by Saylor Innovations On-Chain Data in Onchain & crypto
NFTs a wallet holds in a collection (ERC-721 Enumerable) - balance and token ids, on 5 EVM chains
https://saylorinnovations.com/api/evm/ethereum/nfts/:address/:address2- Price
- $0.005
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 2 h ago, next any minute now
Reliability
Latest check failed 2 h ago: Expected HTTP 402, got 400
How to call it
GET https://saylorinnovations.com/api/evm/ethereum/nfts/:address/:address2
Each call costs $0.005 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
The listing has no example input.
GET https://saylorinnovations.com/api/evm/ethereum/nfts/:address/:address2Example response
The provider's example. We can't check it without paying.
{
"balance": 2,
"chain": "base",
"contract": "0x5555555555555555555555555555555555555555",
"enumerable": true,
"owner": "0x1111111111111111111111111111111111111111",
"token_ids": [
"17",
"4021"
],
"truncated": false
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.005.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://saylorinnovations.com/api/evm/ethereum/nfts/:address/:address2'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://saylorinnovations.com/api/evm/ethereum/nfts/:address/:address2' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.005 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.005" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.005 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fsaylorinnovations.com%2Fapi%2Fevm%2Fethereum%2Fnfts%2F%3Aaddress%2F%3Aaddress2
const res = await pay("https://saylorinnovations.com/api/evm/ethereum/nfts/:address/:address2");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.005 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.005"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://saylorinnovations.com/api/evm/ethereum/nfts/:address/:address2")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 2 h ago | Expected HTTP 402, got 400 | 400 | 553 ms | - |
| 7 h ago | Expected HTTP 402, got 400 | 400 | 1.0 s | - |
| 11 h ago | Expected HTTP 402, got 400 | 400 | 624 ms | - |
| 16 h ago | Expected HTTP 402, got 400 | 400 | 749 ms | - |
| 20 h ago | Expected HTTP 402, got 400 | 400 | 198 ms | - |
Show 10 older checks
| 24 h ago | Expected HTTP 402, got 400 | 400 | 189 ms | - |
| 29 h ago | Expected HTTP 402, got 400 | 400 | 248 ms | - |
| 33 h ago | Expected HTTP 402, got 400 | 400 | 443 ms | - |
| 37 h ago | Expected HTTP 402, got 400 | 400 | 212 ms | - |
| 41 h ago | Expected HTTP 402, got 400 | 400 | 327 ms | - |
| 45 h ago | Expected HTTP 402, got 400 | 400 | 763 ms | - |
| 2 days ago | Expected HTTP 402, got 400 | 400 | 529 ms | - |
| 2 days ago | Expected HTTP 402, got 400 | 400 | 545 ms | - |
| 2 days ago | Expected HTTP 402, got 400 | 400 | 444 ms | - |
| 3 days ago | Expected HTTP 402, got 400 | 400 | 226 ms | - |