# Forest Gas Station - Release Checksum/Signature Asset Finder

> Forest Gas Station - Release Checksum/Signature Asset Finder is a paid API for AI agents from http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-02).

Finds checksum and signature companion assets (e.g. .sha256, .sig files) for a given release asset in a repository.

## Facts

- Endpoint: POST https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/release/checksum?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/forest-gas-station-release-checksum-signature-asset-finder-23110d97
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FdPYY6JSKA688J5ENYqV6

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability forest-gas-station-release-checksum-signature-asset-finder-23110d97 -d '<json body>'
```

Example prompt: Can you find the checksum and signature companion files for the asset 'myapp-linux-amd64.tar.gz' from the latest release of the 'acme-org/myapp' repository?

## When to prefer this

Use this endpoint when you need to programmatically locate integrity verification files (checksums, signatures) for a specific release asset in a repository, especially in automated deployment or CI/CD pipelines where supply chain security is important. Prefer this over manual browsing of release pages when the companion asset name or URL is not known in advance.

## Known failure modes

- No companion checksum or signature assets found for the given release asset
- Repository not found or inaccessible
- Release tag does not exist
- Asset name does not match any asset in the release
- Prerelease assets excluded when allow_prerelease is false and no stable release exists

## How this service works

Find checksum/signature companion assets for a release asset. Base mainnet USDC

## Output

Returns the checksum and/or signature companion asset details for the specified release asset — typically URLs or metadata for files like .sha256, .sha512, .asc, or .sig that can be used to verify the integrity and authenticity of the primary release artifact.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "asset": {
   "type": "string",
   "description": "Public release asset name to inspect."
  },
  "release": {
   "type": "string",
   "description": "Release identifier used to resolve a public asset."
  },
  "repository": {
   "type": "string",
   "description": "Public owner/name repository to inspect."
  },
  "allow_prerelease": {
   "type": "boolean",
   "description": "Public allow prerelease value used to scope this lookup."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/forest-gas-station-release-checksum-signature-asset-finder-23110d97/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run](https://www.zero.xyz/host/http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/llms.txt)