77trust / 100

Near Account Age

by NEAR Account Age & Origin in Markets & finance

x402 APIPassing, checked 4 h ago

Before you trust, pay or copy a NEAR account — or one of the agents on NEAR AI's Agent Market — is it established or created minutes ago? near-account gives the current state; this gives the PROVENANCE: the creation date (age), the creator (first provenance hop), and whether it's since been deleted, from the NearBlocks indexer. Age is a first-order Sybil/trust signal — new ≠ malicious, but a fresh counterparty warrants caution. Pair with near-wallet-activity. Not financial advice.

GET
https://402.com.tr/api/x402/near-account-age
Price
$0.02
per call in USDC
Uptime
100%
last 30 days
Response time
483 ms
589 ms slowest 5%
Last check
Passed
4 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://402.com.tr/api/x402/near-account-age

Each call costs $0.02 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-account-age?account=tether.multisafe.near

Parameters

ParameterTypeRequiredDescription
accountstringYesNEAR account id

Example response

The provider's example. We can't check it without paying.

{
  "ageDays": 1503,
  "checkedAt": "2026-10-13T03:00:54.652Z",
  "createdAt": "2022-08-31T13:51:08.126Z",
  "creatorType": "account",
  "deleted": false,
  "deletedAt": null,
  "verdict": "mature"
}

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

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-account-age?account=tether.multisafe.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-account-age?account=tether.multisafe.near' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: 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.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
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.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2F402.com.tr%2Fapi%2Fx402%2Fnear-account-age
const res = await pay("https://402.com.tr/api/x402/near-account-age?account=tether.multisafe.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.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
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-account-age?account=tether.multisafe.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

WhenResultHTTPTimePrice
4 h agoPassed402552 ms$0.02
9 h agoPassed402513 ms$0.02
14 h agoPassed402407 ms$0.02
18 h agoPassed402589 ms$0.02
23 h agoPassed402554 ms$0.02
Show 10 older checks
27 h agoPassed402498 ms$0.02
31 h agoPassed402469 ms$0.02
35 h agoPassed402368 ms$0.02
39 h agoPassed402372 ms$0.02
44 h agoPassed402574 ms$0.02
2 days agoPassed402491 ms$0.02
2 days agoPassed402450 ms$0.02
2 days agoPassed402549 ms$0.02
3 days agoPassed402460 ms$0.02
3 days agoPassed402341 ms$0.02