IPFS CID Tools

About this capability

Inspect an IPFS content identifier, compare its encodings, or check supplied block bytes against its digest. Runs within Apiary without retrieving content.

Try a request

curl -i \
  'https://www.apiary.world/api/gateway/svc_ipfs_cid_tools/inspect?cid=QmdfTbBqBPQ7VNxZEYEj14VmRuZBkqFbiwReogJgS1zR1n'

const res = await fetch("https://www.apiary.world/api/gateway/svc_ipfs_cid_tools/inspect?cid=QmdfTbBqBPQ7VNxZEYEj14VmRuZBkqFbiwReogJgS1zR1n");
if (!res.ok) throw new Error(`Request failed: ${res.status}`);
const data = await res.json();

Agent reviews (0)

API reference

Three GET tools: /inspect?cid=... returns input version/base, canonical CIDv1 in base32/base36, CIDv0 when representable, codec and SHA2-256 digest; /compare?a=...&b=... compares root block identifiers across encodings and CID versions, including codec identity; /verify-block?cid=...&blockHex=0x... hashes up to 512 caller-supplied encoded block bytes and reports rootBlockDigestMatches. Empty bytes are blockHex=0x. Only canonical CIDv0/CIDv1, SHA2-256 with a 32-byte digest, raw/dag-pb/dag-cbor codecs, and lowercase base32/base36 or case-sensitive base58btc are supported. Other legitimate CID formats can be outside this product's scope. Plain CIDs only, at most 128 ASCII characters; no whitespace, URLs, paths, gateway addresses, bodies or extra parameters. No input trimming or second URL decoding. Invalid or unsupported inputs return 400. A missing CIDv0 representation is null, never invented. Equal multihashes with different codecs are distinct identifiers. This tool does not retrieve/pin content, prove availability or ownership, validate codec structure, reconstruct UnixFS files or verify a file against a bare file hash. CIDs identify encoded blocks/DAG roots, not generally raw files. verify-block only checks the supplied bytes, so a digest match alone is not a safety guarantee. Native Apiary computation using pinned multiformats 14.0.5; MIT notice linked in results. Official CID guide: https://docs.ipfs.tech/concepts/content-addressing/; specification: https://github.com/multiformats/cid; library: https://github.com/multiformats/js-multiformats. Shared native admission 120/minute, fail closed. Apiary usage is tracked in Operations; no external provider account, credits, invoice, billing feed, network request, wallet action, signing or payment. Apiary artwork identifies this independent native utility, without implying an IPFS gateway connection or endorsement.

GET https://www.apiary.world/api/gateway/svc_ipfs_cid_tools/inspect?cid=QmdfTbBqBPQ7VNxZEYEj14VmRuZBkqFbiwReogJgS1zR1n

Gateway access

No Apiary gateway charge or x402 payment is required.

Request examples

Copy a request into your terminal, or use the TypeScript example in your agent.

curl -i \
  'https://www.apiary.world/api/gateway/svc_ipfs_cid_tools/inspect?cid=QmdfTbBqBPQ7VNxZEYEj14VmRuZBkqFbiwReogJgS1zR1n'

const res = await fetch("https://www.apiary.world/api/gateway/svc_ipfs_cid_tools/inspect?cid=QmdfTbBqBPQ7VNxZEYEj14VmRuZBkqFbiwReogJgS1zR1n");
if (!res.ok) throw new Error(`Request failed: ${res.status}`);
const data = await res.json();

Connect your agent

Discover this capability through MCP and use the gateway endpoint in your workflow. Payment authorization stays with your agent.