Back to Browse
VAPE Exploit Check — On-Chain Contract Security Scanner
x402
VAPE Exploit Check — On-Chain Contract Security Scanner is a paid API for AI agents from vape-x402.vapex402.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).
Scans a Base blockchain contract or token address for known exploit patterns and security vulnerabilities, returning audit signals like proxy status, verification state, and contract name.
Price / call$0.01
Success—
StatusUnknown
How this service works
VAPE exploit_check — Contract verification + proxy-swap surface check. Real on-chain/market data, no simulation.
Output
Returns a JSON object containing the contract address, whether it is a proxy contract (boolean), whether it is verified on-chain (boolean), the contract name, and any additional exploit or security signals detected for the given Base address.
Example use cases
Pre-trade token safety check
“Before I swap into this token, can you scan the contract at 0xd9aAEc86B65D86f6A7B5B1b0c42FFA531710b6CA on Base and tell me if it's verified and whether there are any exploit risks I should know about?”
DeFi protocol due diligence
“I'm thinking of depositing funds into a DeFi protocol on Base — can you audit the contract at 0x2Ae3F1Ec7F1F5012CFEab0185bfc7aa3cf0DEc22 and check if it's a proxy contract or has any known vulnerabilities?”
NFT contract security review
“I just got sent an NFT from contract 0x7Fc66500c84A76Ad7e9c93437bFc5Ac33E2DDaE9 on Base — can you scan it for exploits and tell me if the contract is verified before I interact with it?”
Technical details
Endpoint
GEThttps://vape-x402.vapex402.workers.dev/scan/exploit_checkWhen to prefer
Choose this endpoint when you need a quick, pay-per-use on-chain exploit and safety scan specifically for Base (chain 8453) contracts or tokens, without setting up a full audit pipeline. It is ideal for agents that need to dynamically check contract safety before executing a transaction, recommending a DeFi protocol, or displaying token information to users.
Side effects
- Invalid or malformed contract address returns an error or empty result
- Non-existent address on Base chain returns unverified/no contract found
- Unsupported chain ID override may fall back to Base (8453) or fail
- Payment failure via x402 protocol results in 402 status and no scan data
- Rate limiting or worker timeout if scan takes too long for complex contracts
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
Schema · Response
{
"type": "json",
"example": {
"proxy": false,
"address": "0x...",
"verified": true,
"contract_name": "Token"
}
}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"