Skip to main content

Overview

Most honeypot detectors only check a token at the current moment. TxShield’s honeypot endpoint runs time-travel analysis — simulating the token’s behavior across three future time windows to catch traps that activate after launch. A token can show 0% tax right now and 99% sell tax 24 hours later. That’s a time-delayed honeypot, and standard checks miss it entirely.

Endpoint

POST /api/honeypot/honeypot-checks

Request

Headers

Body

Parameters

Supported Chain IDs


Response


Response Fields Explained

Top Level


honeypotResponse


timeTravelResults[] — Each Time Window


How to Read the Results

The Safe Token

All three windows consistent. No flags. Safe to proceed.

The Time-Delayed Honeypot

Looks tradeable right now. By 24 hours, sell tax hits 99% — users are trapped. isTimeHoneypot: true is your block signal.

The Blacklist Trap

Tax looks fine. But blacklist activates at 24 hours — owner can block any wallet from selling at any time.

Risk Score Reference

Always check isTimeHoneypot alongside riskScore. A token can have a moderate score at the "Immediate" window but become Critical Risk by "7 Days". The time-travel delta is the most important signal.

Code Examples


Error Responses


EVM Simulation

Run a full simulation with bytecode analysis alongside honeypot detection.

Authentication

How to generate and use your API key.