Verdict Base
by micro-saas-agent.onrender.com in Onchain & crypto
Is this token safe? Score 0-100 and verdict safe/caution/danger with reasons and source URLs, from GoPlus token security + DexScreener liquidity using fixed published rules. Chains: base, ethereum, bsc, arbitrum, solana. 10-min cache. $0.02.
https://micro-saas-agent.onrender.com/api/verdict/base/:address- Price
- $0.02
- 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
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://micro-saas-agent.onrender.com/api/verdict/base/:address
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://micro-saas-agent.onrender.com/api/verdict/base/:addressExample response
The provider's example. We can't check it without paying.
{
"address": "0x...",
"chain": "base",
"reasons": [
"-15: mintable"
],
"score": 85,
"sources": [
"https://api.gopluslabs.io/...",
"https://api.dexscreener.com/..."
],
"verdict": "safe"
}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://micro-saas-agent.onrender.com/api/verdict/base/:address'
# 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://micro-saas-agent.onrender.com/api/verdict/base/:address' \
| 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.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%2Fmicro-saas-agent.onrender.com%2Fapi%2Fverdict%2Fbase%2F%3Aaddress
const res = await pay("https://micro-saas-agent.onrender.com/api/verdict/base/:address");
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://micro-saas-agent.onrender.com/api/verdict/base/:address")
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 | 197 ms | - |
| 5 h ago | Expected HTTP 402, got 400 | 400 | 163 ms | - |
| 14 h ago | Expected HTTP 402, got 400 | 400 | 136 ms | - |