Near Transfer Preflight
by NEAR Transfer Preflight in Onchain & crypto
Before sending a NEP-141 token on NEAR: is the token real and not paused, does the receiver exist, and is it registered on the token — the storage_deposit step whose absence fails a transfer. If not, says the exact fix and its NEAR cost. With from and amount, also checks the sender holds enough. Catches sending to the token contract itself. Live from the NEAR RPC.
https://402.com.tr/api/x402/near-transfer-preflight- Price
- $0.01
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 509 ms
- 646 ms slowest 5%
- Last check
- Passed
- 6 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://402.com.tr/api/x402/near-transfer-preflight
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.
GET https://402.com.tr/api/x402/near-transfer-preflight?amount=25&from=bob.near&to=tether.multisafe.near&token=usdt.tether-token.nearParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
amount | string | No | Amount in token units (optional) |
from | string | No | Sender NEAR account (optional) |
to | string | Yes | Receiver NEAR account |
token | string | Yes | NEAR token contract account |
Example response
The provider's example. We can't check it without paying.
{
"amount": "25",
"chain": "near",
"checkedAt": "2026-10-08T08:47:10.793Z",
"checksCount": 4,
"fromBalance": "0.097688",
"verdict": "STOP"
}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 'https://402.com.tr/api/x402/near-transfer-preflight?amount=25&from=bob.near&to=tether.multisafe.near&token=usdt.tether-token.near'
# 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://402.com.tr/api/x402/near-transfer-preflight?amount=25&from=bob.near&to=tether.multisafe.near&token=usdt.tether-token.near' \
| 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%2F402.com.tr%2Fapi%2Fx402%2Fnear-transfer-preflight
const res = await pay("https://402.com.tr/api/x402/near-transfer-preflight?amount=25&from=bob.near&to=tether.multisafe.near&token=usdt.tether-token.near");
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.get("https://402.com.tr/api/x402/near-transfer-preflight?amount=25&from=bob.near&to=tether.multisafe.near&token=usdt.tether-token.near")
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 |
|---|---|---|---|---|
| 6 h ago | Passed | 402 | 540 ms | $0.01 |
| 16 h ago | Passed | 402 | 514 ms | $0.01 |
| 26 h ago | Passed | 402 | 357 ms | $0.01 |
| 36 h ago | Passed | 402 | 469 ms | $0.01 |
| 40 h ago | Passed | 402 | 467 ms | $0.01 |
Show 10 older checks
| 45 h ago | Passed | 402 | 503 ms | $0.01 |
| 2 days ago | Passed | 402 | 643 ms | $0.01 |
| 2 days ago | Passed | 402 | 455 ms | $0.01 |
| 2 days ago | Passed | 402 | 488 ms | $0.01 |
| 3 days ago | Passed | 402 | 477 ms | $0.01 |
| 3 days ago | Passed | 402 | 827 ms | $0.01 |
| 3 days ago | Passed | 402 | 583 ms | $0.01 |
| 3 days ago | Passed | 402 | 455 ms | $0.01 |
| 3 days ago | Passed | 402 | 541 ms | $0.01 |
| 3 days ago | Passed | 402 | 438 ms | $0.01 |