Back to Browse
Orchard Data Token Check
x402
Orchard Data Token Check is a paid API for AI agents from orchard-data.letom1176.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-16).
Analyzes a cryptocurrency token contract address for security risks, honeypot status, liquidity, and market data on EVM chains
Price / call$0.005
Success—
StatusUnknown
How this service works
Market data and agent tools (web-read, email-verify, token-check) for AI agents, paid per-call via x402 (USDC on Base). Free index at /, free spec here.
Output
Returns a JSON object with a numeric security score (0-100), market data (symbol, liquidity in USD), a verdict string (e.g. 'no_major_flags'), boolean honeypot indicator, sell tax percentage, and arrays of warnings and red flags for the queried token contract on the specified chain.
Example use cases
Pre-trade token safety check
“Before I buy this token, can you check if 0x532f27101965dd16442E59d40670FaF5eBB142E4 on Base is a honeypot or has any major red flags I should know about?”
DeFi rug pull detection
“I found a new token on Ethereum at 0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984 — can you run a security scan on it and tell me the liquidity, sell tax, and any warnings?”
Arbitrage bot token vetting
“Check the security score and honeypot status for token contract 0xB64E638E60D154B43f660a6BF8fD8a7b9DAC93A3 on Arbitrum before I include it in my trading strategy.”
Technical details
Endpoint
GEThttps://orchard-data.letom1176.workers.dev/api/token-check?utm_source=zero.xyzWhen to prefer
Use this endpoint when an AI agent needs to quickly vet an unknown EVM token contract before trading, investing, or including it in a DeFi workflow. It combines honeypot detection, sell tax analysis, liquidity data, and a composite security score in a single call, making it ideal for automated pre-trade safety checks across Base, Ethereum, BSC, Arbitrage, Polygon, and Optimism.
Side effects
- Invalid or non-existent contract address returns an error or empty result
- Unsupported chain identifier causes a bad request
- Token with no on-chain data may return incomplete market fields
- Network timeouts on slow RPC responses
- Payment failure via x402 if USDC balance is insufficient (HTTP 402)
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
Schema · Response
{
"type": "json",
"example": {
"chain": "base",
"score": 100,
"market": {
"symbol": "BRETT",
"liquidity_usd": 771058
},
"verdict": "no_major_flags",
"security": {
"is_honeypot": false,
"sell_tax_pct": 0
},
"warnings": [],
"red_flags": []
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"