13trust / 100

Polygon Token

by Saylor Innovations Watchdog API in Onchain & crypto

x402 APIFailing, checked 42 min ago

Honeypot check and token risk score for a Polygon token contract address - can you sell it, buy and sell tax, owner privileges, rug pull signals and a 0-100 verdict

GET https://saylorinnovations.com/api/polygon/token/:address

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
0.0%
Response time
- typical, - slowest 5%
Last check
42 min ago: Expected HTTP 402, got 400
Next check
in 17 min

How to call it

GET https://saylorinnovations.com/api/polygon/token/:address

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

The listing has no example input.

GET https://saylorinnovations.com/api/polygon/token/:address

Example response

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

Example response, 32 lines
{
  "address": "0xD6DF932A45C0f255f85145f286eA0b292B21C90B",
  "card": "TOKEN · SOLID · 88/100 — No honeypot, tax or ownership red flags found",
  "chain": "polygon",
  "fetched_at": "2026-10-12T00:00:00.000Z",
  "grade": "SOLID",
  "headline": "TOKEN shows no honeypot, tax or ownership red flags and trades with deep liquidity.",
  "market": {
    "liquidity_usd": 1000000,
    "volume_24h_usd": 250000
  },
  "name": null,
  "one_liner": "No honeypot, tax or ownership red flags found",
  "reasons": [
    "Contract source is verified",
    "No buy/sell tax",
    "Liquidity $1.0M in the top pair"
  ],
  "score": 88,
  "security": {
    "buy_tax": 0,
    "is_honeypot": false,
    "sell_tax": 0
  },
  "sources_failed": [],
  "sources_ok": [
    "goplus",
    "dexscreener"
  ],
  "symbol": null,
  "verdict": "looks-ok"
}

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://saylorinnovations.com/api/polygon/token/: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://saylorinnovations.com/api/polygon/token/:address' \
  | 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.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%2Fsaylorinnovations.com%2Fapi%2Fpolygon%2Ftoken%2F%3Aaddress
const res = await pay("https://saylorinnovations.com/api/polygon/token/: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.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://saylorinnovations.com/api/polygon/token/: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

WhenResultHTTPTimePrice
42 min agoExpected HTTP 402, got 400400256 ms-
5 h agoExpected HTTP 402, got 400400912 ms-
10 h agoExpected HTTP 402, got 400400747 ms-
15 h agoExpected HTTP 402, got 400400329 ms-
19 h agoExpected HTTP 402, got 4004001.2 s-
23 h agoExpected HTTP 402, got 400400376 ms-
28 h agoExpected HTTP 402, got 400400926 ms-
32 h agoExpected HTTP 402, got 400400260 ms-
36 h agoExpected HTTP 402, got 400400726 ms-
40 h agoExpected HTTP 402, got 400400250 ms-
43 h agoExpected HTTP 402, got 400400318 ms-
2 days agoExpected HTTP 402, got 400400202 ms-