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.
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:
- can an agent safely prepare to run this paid Apify Actor
- check Apify Actor pricing and input before spending money
- validate a proposed automation input before an agentic paid run
What Forest guarantees
- at most two bounded public GET requests to fixed Apify metadata surfaces
- no Actor run, credit purchase, authentication, mutation or external payment
- no invented total cost or runtime estimate when public metadata cannot prove one
Boundaries
- successful future Actor execution
- exact final run cost when event counts or usage are unknown
- exact runtime or quality of Actor output
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.
- 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.
- Email Verify — Verify email syntax and public DNS readiness with a bounded deterministic preflight. Forest checks normalized syntax, MX/address records including explicit null MX, and curated role/free/disposable-domain signals, then returns a conservative safe-to-attempt decision. It never connects to SMTP, sends mail, authenticates, stores customer mailboxes or claims that a mailbox exists.