For the complete documentation index, see llms.txt. This page is also available as Markdown.

How to Check Tokens For Rug Pull Risk Before Listing with GetBlock Rug Pull Checker API

This guide shows you how to check token for rug pull risk with GetBlock Rug Pull Checker API

Listing a token is a promise to your users: "we vetted this." But a contract can hide a honeypot that lets people buy and never sell, a mint function that dilutes holders overnight, or a 40% sell tax buried in the code — and the creator's wallet may have rugged three tokens already.

The GetBlock Rug Pull Check API runs both analyses at once: an AI-based probability assessment using the creator's and liquidity providers' on-chain history, and a contract-level scan of taxes, owner privileges, honeypot traps, and holder concentration.

In this guide, you'll build a token-vetting gate that returns a clear GO/NO-GO verdict before you list a token (or before a user imports it), along with the specific red flags that drove the decision.

Eyeballing the contract
Rug Pull Check gate

You can't see the creator's history

AI probability from creator + LP behavior

Honeypots look like normal tokens

is_honeypot, cannot_sell_all flagged explicitly

Hidden taxes / mint rights are easy to miss

Taxes and owner privileges returned as fields

"Who holds this?" — manual digging

Top-10 holders with % concentration

What you'll build

A vetToken(contractAddress, network) function that:

  1. Sends the contract to the Rug Pull Check endpoint.

  2. Reads the AI rug-pull probability and the API's Fraud verdict.

  3. Collects concrete red flags — honeypot, mint rights, high taxes, holder concentration.

  4. Returns GO (safe to list) or NO-GO (block) with the reasons.

How it works

This endpoint is for contracts only — passing a wallet (EOA) returns empty results. The AI probability is behavioral (creator/LP history) and does not read the contract code; the risk_indicators block is the code-level scan. Use both together.

Prerequisites

Project Setup

1

Set up the project

2

Get your API key

  1. Open Address Audit → API keys.

  2. Copy your key and save it in an .env file

3

Vet a known contract (USDT) to confirm your key and the endpoint:

Field
Value
Notes

Authorization

Bearer <key>

Your Risk & Compliance API key.

network

ETH

Uppercase: ETH, BNB, or BASE.

contract_address

token contract

snake_case field name. EOAs return empty results.

A successful response (trimmed):

Numeric flags are 0 (clean) or 1 (detected). buy_tax/sell_tax are fractions (multiply by 100 for a percentage). holder_count, holder percent, and probabilityFraud come back as strings.

4

Write the API caller

Create rugpull.js. Note the network is normalized to uppercase here so callers can pass eth, ETH, or ethereum.

5

Collect the red flags

The API gives you dozens of indicators. Create flags.js to turn them into a human-readable list, grouped by severity. Tune the thresholds to your own policy.

6

Make the GO / NO-GO decision

Create vet.js. It blocks on the API's own Fraud verdict, a HIGH AI probability, or any disqualifying red flag.

7

Run it

Create index.js:

Expected output for a clean token:

Notice the verdict is NO-GO even though the AI probability is LOW — the is_mintable flag tripped your policy. The two analyses are independent: a clean AI score does not cancel out a dangerous contract privilege. Tune flags.js to decide which privileges are dealbreakers for your platform.

Understanding the response

Field
Type
What it tells you

status

"Fraud" | "Not Fraud"

Top-level verdict.

probabilityFraud

string 0–1

AI rug-pull probability (creator/LP behavior).

risk_score / risk_status

number / label

Combined score and human label (e.g. "High Risk").

risk_indicators

object

Code-level scan: taxes, honeypot, mint/owner rights, liquidity, holders[].

forensic_details

object

Contract findings: is_open_source, selfdestruct, approval_abuse, owner type.

Troubleshooting

Symptom
Likely cause
Fix

HTTP 400

Wrong network case or field name

Use uppercase ETH/BNB/BASE and contract_address.

Empty / null result

You passed a wallet, not a contract

Rug Pull works on contracts only.

Unsupported network error

Polygon / Tron not covered

Rug Pull supports ETH, BNB, BASE only.

HTTP 401 / 403

Bad key / no Address Audit access

Re-check GETBLOCK_KEY and your plan.

HTTP 402 / 429

Out of quota / rate limited

Free tier is 5/day; back off or top up.

Conclusion

You built a token-vetting gate that calls the GetBlock Rug Pull Check API directly, combines AI behavioral probability with a code-level contract scan, and returns a GO/NO-GO verdict along with the exact red flags behind it. Drop vetToken into your listing pipeline, a "before you import this token" warning in a wallet, or a CLI your team runs against a candidate list — and fail closed whenever a check can't complete.

Resources

Last updated

Was this helpful?