# ForgeMesh File Checksum Verifier

> ForgeMesh File Checksum Verifier is a paid API for AI agents from x402.forgemesh.io, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-13).

Fetches any public file URL (up to 50MB) and returns its SHA-256, SHA-512, SHA-1, or MD5 hex digest so agents can verify a download matches its published checksum before trusting it.

## Facts

- Endpoint: POST https://x402.forgemesh.io/verify-file-checksum
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/forgemesh-file-checksum-verifier-7ebe6be4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SAGLampW_FsVndovT1mM9

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 forgemesh-file-checksum-verifier-7ebe6be4 -d '<json body>'
```

Example prompt: Before we install that PyTorch wheel, can you verify that https://files.pythonhosted.org/packages/torch-2.3.0-cp310-linux.whl has a SHA-256 hash matching a9f3c2e1 — fetch the file and return the full hex digest so I can compare?

## When to prefer this

Use this endpoint when an AI agent needs to verify a remote file's integrity before installing, executing, or trusting it — especially for packages, model weights, or binaries downloaded as part of an automated workflow. Prefer this over computing hashes locally when the agent cannot download the file directly or needs a neutral third-party hash computation.

## Known failure modes

- File URL is not publicly accessible or returns a non-200 status — API returns an error
- File exceeds the 50MB size limit — API returns a size limit error
- Unsupported algorithm specified — API returns a validation error
- Network timeout fetching the remote file — API returns a timeout error
- Invalid or malformed URL provided — API returns a bad request error

## How this service works

File checksum API: fetch any public file URL (up to 50MB) and return its SHA-256/SHA-512/SHA-1/MD5 hex digest — verify a download matches its published checksum BEFORE trusting it. Supply-chain safety for agents installing packages, models, and binaries. File is hashed in memory and discarded.

## Output

A hex-encoded cryptographic digest (SHA-256 by default, or SHA-1/SHA-512/MD5 if specified) of the fetched file, confirming or allowing comparison against a known published checksum. The file is hashed in-memory and discarded after computation.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string"
  },
  "algorithm": {
   "type": "string",
   "description": "sha256 default"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "hex": "eefffad4e662b2821b1aab5957d4dcc60ac6e19fd5523ec59dad6d29deac64e1",
  "bytes": 53647,
  "algorithm": "sha256"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/forgemesh-file-checksum-verifier-7ebe6be4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.forgemesh.io](https://www.zero.xyz/host/x402.forgemesh.io/llms.txt)