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.
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:
- get the current gas fee snapshot on Base
- check Ethereum base fee and priority fee before a transaction
- read current EIP 1559 fee history for an EVM chain
- check current p25 p50 p90 priority fees
- get current gas conditions before broadcasting elsewhere
What Forest guarantees
- fixed supported chain allowlist only: ethereum, optimism, bnb, polygon, base, arbitrum, avalanche; callers cannot supply an RPC URL or arbitrary chain id
- exactly one eth_feeHistory JSON-RPC method on a cold refresh with fixed block count 4 and percentiles 25/50/90
- process-shared 5000 ms per-chain cache with same-chain single-flight refresh
- provider-wide process-local pacing of at least 1000 ms between cold refreshes with at most 16 queued refresh slots before fail-fast busy
- fee quantities are parsed as hexadecimal integers into exact decimal strings; they are not round-tripped through binary floating point
- fixed keyless SolidRPC public EVM endpoint with no credentials, wallet, transaction signing, simulation, broadcast, arbitrary JSON-RPC method or provider fallback
Boundaries
- transaction-specific gas limit, total transaction cost, executable fee quote or guaranteed inclusion time
- optimal slow/standard/fast tier recommendation or automatic fee selection for the caller
- cross-chain cheapest-fee comparison, native-token USD conversion or token-price lookup
- archive/log indexing, arbitrary JSON-RPC proxying or transaction submission
- 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
- 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.
- 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.