Release Asset-resolve
Resolve a public GitHub release into the most plausible downloadable asset for a normalized OS/architecture target, excluding source/signature/checksum files and linking checksum companions when present. Returns ambiguity instead of silently choosing tied candidates. No private repositories or customer authentication.
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:
- find windows x64 release binary
- resolve GitHub release asset
- find correct download for linux arm64
What Forest guarantees
- deterministic public GitHub asset ranking
- explicit ambiguity instead of silent tie-breaking
Boundaries
- asset runtime compatibility
- binary safety
- private repositories
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
- Release Changed — Fingerprint the normalized metadata state of one public GitHub release and optionally compare it with a caller-provided previous SHA-256 hash. Forest uses the existing bounded release lookup and does not download assets, inspect repository contents or mutate GitHub state.
- Release Checksum — Find checksum/signature companion assets for a release asset.
- Release Preflight — Check whether a repository has a usable latest/tagged release before deployment/download.
- Package Preflight — Verify whether a specific npm or PyPI package version exists before installation, resolve the current/latest version, and report deprecation or yank state when available, plus license and runtime requirement. This is a public-registry package install preflight; it does not resolve dependency graphs or perform vulnerability analysis.
- Repo Branch-state — Check whether a named branch exists in a public GitHub repository and return the branch current head commit SHA and URL without cloning. This is a read-only branch-state lookup; branch protection stays unknown when the public API does not expose it.