Token Risk-preflight
Return bounded third-party ERC-20 security evidence for one exact contract on a fixed supported EVM chain using the GoPlus Token Security API. Forest normalizes named control, trading-restriction and tax facts into conservative evidence classes; it does not claim a token is safe, audit source code, predict returns, recommend a trade, access a wallet, approve, swap, sign, simulate or broadcast a transaction.
Forest exposes this capability as a deterministic machine-readable API for software agents. Discovery is free; execution uses the canonical paid endpoint below. The live x402 challenge is the source of truth for payment terms.
Typical agent tasks
This capability is intended for bounded machine decisions such as:
- check an ERC20 token before buying it
- is this EVM token reported as a honeypot or hard to sell
- check token buy and sell tax before a swap
- check mint blacklist pause proxy and ownership controls on a token
- run a token risk preflight before approval or trade
What Forest guarantees
- fixed supported EVM chain allowlist only: ethereum, optimism, bnb, polygon, base, arbitrum; callers cannot supply a provider URL or arbitrary chain id
- one exact GoPlus single-token security GET per cold chain/address refresh with a process-shared 30000 ms cache and same-key single-flight
- provider-wide process-local pacing of at least 2500 ms between cold refreshes with at most 16 queued refresh slots before fail-fast busy
- provider 0/1/empty/missing security fields are normalized as false/true/unknown; unknown evidence is never silently coerced to false
- block_evidence is limited to explicit severe upstream facts configured by Forest; review covers caution facts or incomplete security evidence; clear_evidence is not a safety guarantee
- fixed public GoPlus Token Security endpoint only, with no provider credentials, wallet, signing, transaction simulation, approval, swap, broadcast, arbitrary API relay or provider fallback
Boundaries
- proof that a token is safe, trustworthy, non-ruggable, profitable, liquid or sellable under every future state
- source-code audit, holder/deployer forensics, liquidity history, exploit detection, malware scanning or multi-provider security consensus
- price prediction, investment advice, trade direction, expected return, execution quote or transaction-specific simulation
- coverage of Solana/SPL or arbitrary unsupported chains
- global cross-replica rate limiting; cache, single-flight and provider pacing are process-local
Machine contract
The request and response schemas are published in the canonical OpenAPI document. This page shows a representative input from the same production manifest.
Input example
Canonical paid endpoint
Related capabilities
- Chain Gas-snapshot — Return one bounded current EVM fee-history snapshot for a fixed supported chain using SolidRPC public JSON-RPC. Forest reports recent base-fee and latest sampled-block priority-fee percentile evidence only; it does not estimate a caller transaction gas limit, simulate, sign or broadcast a transaction, access a wallet, choose a transaction fee for the caller or guarantee an optimal fee.
- Automation Preflight — Preflight one public Apify Actor before a paid automation run using only public Store and default-build OpenAPI metadata. Forest checks agentic-payment eligibility, pricing/budget signals and top-level input compatibility without starting an Actor, buying credit, authenticating or making an external payment.
- Commerce Purchase-preflight — Combine public product resolution, one fresh isolated anonymous cart, optional delivery lookup and checkout handoff evidence into one bounded purchase preflight. Shopify Ajax and WooCommerce Store API are supported; Forest never logs in, touches a customer session, creates an order or attempts payment.
- Container Pull-preflight — Preflight one anonymously readable OCI image for a requested target platform before pull or deploy. Forest resolves the supplied tag once, selects one exact multi-arch child manifest when possible, reports that immutable manifest declared config/layer size, and checks bounded OCI referrer presence. No layers are downloaded and referrer presence is never treated as signature, SBOM, attestation or vulnerability verification.
- Cors Preflight — Send exactly one bounded non-credentialed browser-style CORS OPTIONS preflight to the supplied public URL and normalize the observed Access-Control-Allow-* response into origin, method and header decisions. Redirects are not followed, so the result describes the exact resource URL. Forest does not send cookies or Authorization, invoke the requested resource afterward, run JavaScript, or guarantee browser/runtime success beyond the observed response.
- Domain Preflight — Resolve a bare public domain into operational registration, DNS, HTTPS/TLS and mail-policy state using IANA-routed RDAP, DNS, MX/TXT/SPF/DMARC and a bounded TLS probe. No registrant personal data, vulnerability scanning, mailbox existence or deliverability claim. Provider uncertainty is explicit.