Security Contract Health Audit

Last 30 days

Uptime

100%

Response time

125 ms typical, 185 ms slowest 5%

Last check

2 h ago

Next check

any minute now

How to call it

# See the payment challenge (nothing is charged)
curl -i -X GET "https://alphapipeline-eu.onrender.com/v1/security/contract-health-audit?chain_id=8453&contract_address=0x532f27101965dd16442e59d40670faf5ebb142e"

import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { ExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

const client = new x402Client().register(
  "eip155:8453",
  new ExactEvmScheme(privateKeyToAccount(process.env.AGENT_KEY)),
);
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? Preflight it first for $0.005:
// GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Falphapipeline-eu.onrender.com%2Fv1%2Fsecurity%2Fcontract-health-audit
const res = await pay("https://alphapipeline-eu.onrender.com/v1/security/contract-health-audit?chain_id=8453&contract_address=0x532f27101965dd16442e59d40670faf5ebb142e");
console.log(await res.json());

Example input

{
  "chain_id": 8453,
  "contract_address": "0x532f27101965dd16442e59d40670faf5ebb142e"
}

Example output

{
  "chain_id": 8453,
  "contract_address": "0x532f27101965dd16442e59d40670faf5ebb142e",
  "data_source": "goplus",
  "generated_at": {
    "kst": "2026-09-07 21:00:00 KST",
    "utc": "2026-09-07T12:00:00Z"
  },
  "liquidity_health": "LOCKED",
  "lp_burned_pct": 98.7,
  "lp_holder_count": 3,
  "lp_locked_pct": 0,
  "lp_total_supply": 128500.42,
  "notice": "LP lock/burn detection comes from GoPlus Security's lp_holders field, which flags an address as is_locked only when GoPlus recognizes it as a known third-party locker contract (e.g. Unicrypt, Team.Finance) - coverage varies by chain and is generally weaker outside Ethereum/BSC, so a low lp_locked_pct can mean 'actually unlocked' or just 'GoPlus doesn't recognize this locker'. Burn addresses are matched against a small known list and are always counted as permanently secured. This tool checks LP lock/burn status only - it does not re-run the honeypot/tax checks from security.token_risk, and it does not evaluate transaction history for suspicious activity. Always cross-verify on a block explorer before trusting liquidity as safe.",
  "risk_flags": [],
  "token_name": "Example Token",
  "token_symbol": "EXTKN",
  "top_unlocked_holder_pct": 1.1
}

Security scan

• No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks