Deploy Readiness
Compose bounded DNS propagation, TLS validity and HTTP health observations into one conservative deployment-readiness state. Optional DNS change evidence is included when a previous hash is supplied; this is not a deployment guarantee or worldwide propagation claim.
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.
$0.006 / callPOST /deploy/readinessx402 · Base
Typical agent tasks
This capability is intended for bounded machine decisions such as:
- is this deployment ready after DNS changed
- check DNS TLS and HTTP readiness after deployment
- can I proceed after deploying this hostname
What Forest guarantees
- bounded DNS propagation, TLS and HTTP observations in one request
- conservative readiness classification with explicit blockers and warnings
Boundaries
- worldwide DNS propagation
- deployment success guarantee
- application correctness beyond the observed HTTP response
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
{
"hostname": "http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run",
"record_type": "A",
"url": "https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/health"
}
Canonical paid endpoint
https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/deploy/readiness
Related capabilities
- Dns Consensus — Compare one public DNS record type across a fixed bounded set of independent public DNS-over-HTTPS resolvers. Answers, TTL ranges and resolver disagreement are normalized; this is not an authoritative or worldwide DNS view.
- Dns Propagation — Check whether a DNS change has reached the configured public resolvers. Compare public DoH answers with an optional expected answer set and return complete, partial, not_observed or unknown. Scope is a fixed bounded resolver set; Forest does not claim worldwide propagation.
- Dns Snapshot — Fetch one bounded public DNS snapshot for A, AAAA, CNAME, MX, NS, SOA and TXT in a single call. Forest uses a fixed public DNS-over-HTTPS resolver, distinguishes answers, NODATA, NXDOMAIN and per-type resolver errors, and marks mixed trustworthy/error outcomes as partial instead of converting resolver failure into an empty DNS result.
- Api Readiness — Compose bounded API discovery with one deterministic OpenAPI or Swagger preflight into a concise agent-readiness state. The check does not authenticate, call discovered API operations, or prove business-level API correctness.
- 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.