Agent Credit Score
by Agent Credit Score & FICO in Onchain & crypto
🆕 Evaluates an onchain AI agent's transaction history, solvency, ETH/USDC reserves, and Builder Code activity to compute a FICO-style credit score (300-850), trust tier (AAA to F), and approved postpaid micro-credit limit on Base. Eligible agents qualify for batch-settled zero-latency API calls and EAS onchain attestations. Pass address= (agent wallet or contract).
GET https://402.com.tr/api/x402/agent-credit-score
Last 30 days
Status and outage history · Atom feed
- Uptime
- 60.0%
- Response time
- 455 ms typical, 486 ms slowest 5%
- Last check
- 1 h ago: Expected HTTP 402, got 404
- Next check
- in 3 min
How to call it
GET https://402.com.tr/api/x402/agent-credit-score
Each call costs $0.04 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/agent-credit-score?address=0x973a31858f4d2125f48c880542da11a2796f12d6Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
address | string | Yes | Agent address to score |
Example response
The provider's example. We can't check it without paying.
{
"address": "0x973A31858f4D2125f48C880542DA11a2796f12D6",
"checkedAt": "2026-10-13T03:00:58.901Z",
"creditScore": 620,
"postpaidCreditLimitUsd": 5,
"ratingTier": "B"
}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.04.
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/agent-credit-score?address=0x973a31858f4d2125f48c880542da11a2796f12d6'
# 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/agent-credit-score?address=0x973a31858f4d2125f48c880542da11a2796f12d6' \
| 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.04 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.04" });
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.04 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2F402.com.tr%2Fapi%2Fx402%2Fagent-credit-score
const res = await pay("https://402.com.tr/api/x402/agent-credit-score?address=0x973a31858f4d2125f48c880542da11a2796f12d6");
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.04 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.04"})
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/agent-credit-score?address=0x973a31858f4d2125f48c880542da11a2796f12d6")
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 |
|---|---|---|---|---|
| 1 h ago | Expected HTTP 402, got 404 | 404 | 147 ms | - |
| 6 h ago | Expected HTTP 402, got 404 | 404 | 175 ms | - |
| 9 h ago | Expected HTTP 402, got 404 | 404 | 170 ms | - |
| 13 h ago | Expected HTTP 402, got 404 | 404 | 160 ms | - |
| 17 h ago | Passed | 402 | 455 ms | $0.04 |
| 21 h ago | Passed | 402 | 486 ms | $0.04 |
| 25 h ago | Passed | 402 | 502 ms | $0.04 |
| 29 h ago | Passed | 402 | 464 ms | $0.04 |
| 32 h ago | Passed | 402 | 349 ms | $0.04 |
| 41 h ago | Passed | 402 | 455 ms | $0.04 |