Tools Balance
by Base Pulse in Onchain & crypto
Run before sending ETH or USDC or paying gas, to confirm the wallet really has enough. Never trust a balance remembered from earlier in a chat. Reads a wallet's ETH and native USDC balance on Base directly from the chain, at one block.
https://base-pulse-1021990235790.us-central1.run.app/api/tools/balance- Price
- $0.01
- 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: Served content without asking for payment
Status and outage history · Atom feed · Watch with other listings
How to call it
POST https://base-pulse-1021990235790.us-central1.run.app/api/tools/balance
Each call costs $0.01 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
From the listing.
POST https://base-pulse-1021990235790.us-central1.run.app/api/tools/balance
content-type: application/json
{
"wallet": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
network | string | No | One of: base, base-sepolia. Default: "base". |
wallet | string | Yes |
Example response
The listing has no example response.
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.01.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://base-pulse-1021990235790.us-central1.run.app/api/tools/balance' \
-H 'content-type: application/json' \
--data-raw '{"wallet":"0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"}'
# 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 - -X POST 'https://base-pulse-1021990235790.us-central1.run.app/api/tools/balance' \
-H 'content-type: application/json' \
--data-raw '{"wallet":"0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"}' \
| 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.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
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.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fbase-pulse-1021990235790.us-central1.run.app%2Fapi%2Ftools%2Fbalance&method=POST
const res = await pay("https://base-pulse-1021990235790.us-central1.run.app/api/tools/balance", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"wallet": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
}),
});
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.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://base-pulse-1021990235790.us-central1.run.app/api/tools/balance",
json={
"wallet": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
},
)
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 | Served content without asking for payment | 200 | 445 ms | - |
| 6 h ago | Served content without asking for payment | 200 | 528 ms | - |
| 11 h ago | Served content without asking for payment | 200 | 693 ms | - |
| 16 h ago | Served content without asking for payment | 200 | 485 ms | - |
| 22 h ago | Served content without asking for payment | 200 | 453 ms | - |
Show 10 older checks
| 28 h ago | Served content without asking for payment | 200 | 544 ms | - |
| 33 h ago | Served content without asking for payment | 200 | 569 ms | - |
| 39 h ago | Served content without asking for payment | 200 | 476 ms | - |
| 44 h ago | Served content without asking for payment | 200 | 433 ms | - |
| 2 days ago | Served content without asking for payment | 200 | 379 ms | - |
| 2 days ago | Served content without asking for payment | 200 | 624 ms | - |
| 3 days ago | Served content without asking for payment | 200 | 535 ms | - |
| 3 days ago | Served content without asking for payment | 200 | 455 ms | - |
| 3 days ago | Served content without asking for payment | 200 | 422 ms | - |
| 3 days ago | Served content without asking for payment | 200 | 657 ms | - |