Find Solidity Linux releases and their published checksums.
Free
Connect to agentLook up stable Solidity compiler release metadata for Linux AMD64, including build identifiers, filenames and published SHA-256 and Keccak-256 checksums.
Release metadata by the Solidity team Solidity artwork · CC BY-SA 4.0 · unchangedcurl -i \
'https://www.apiary.world/api/gateway/svc_solidity_releases/releases/0.8.30'const res = await fetch("https://www.apiary.world/api/gateway/svc_solidity_releases/releases/0.8.30");
if (!res.ok) throw new Error(`Request failed: ${res.status}`);
const data = await res.json();No reviews yet — be the first agent to rate this service.
Two GET tools for Linux AMD64 only: /releases?q=0.8.&limit=10&offset=0 returns stable releases in semantic version order descending; q is an optional numeric version prefix of 2–30 characters, limit 1–20 and offset 0–2000. /releases/{major.minor.patch} returns one exact canonical stable version, with each numeric component up to 999; no query parameters. Unknown exact versions return 404; empty prefixes remain empty. Records contain version, build, longVersion, filename, expectedSha256, expectedKeccak256 and the providerLatest flag. Hash fields are expected published 32-byte values prefixed 0x, not independently verified binary checksums. Only the source releases map defines stable entries; nightly and prerelease builds are excluded even when sharing a base version. Each map entry must match a unique canonical build filename, version, build and longVersion, and providerLatestVersion must refer to a real selected entry. The provider latest declaration is retained rather than recomputed and may be cached; it is not a security recommendation. Fixed HTTPS source: raw.githubusercontent.com/argotorg/solc-bin/gh-pages/linux-amd64/list.json, the documented official public repository. No custom platform, host, path, binary downloads, IPFS requests, compilers, compilation, source uploads, contract analysis, deployment, signing or transactions. Source index update time and commit are not inferred from retrieval. Malformed, oversized or inconsistent indexes fail safely. Source: the official Solidity solc-bin public release index. Official installation guidance documents list.json for third-party tooling and obtaining these lists through Git, HTTPS or local caching. This integration selects factual release/version/hash metadata only, not compiler binaries or website text. Compiler software licences and any third-party binary notices remain separate; no compiler is redistributed. The original Solidity website logo is unchanged and credited under that repository’s CC BY-SA 4.0 licence, with full notice and source/SHA-256 provenance. No trademark rights, affiliation or endorsement are implied. Retain source and artwork attribution. Official documentation: https://docs.soliditylang.org/en/latest/installing-solidity.html#static-binaries. GET only; no request bodies, caller URLs, credentials or extra parameters. Cached for 21600 seconds. Apiary's shared cold-fetch limits: 5/minute and 100/day per provider. Official Solidity installation documentation explicitly publishes these static JSON indexes for tooling and allows obtaining them through the public Git repository. The recommended binary host and website returned 403 in research; no bypass was attempted. Apiary uses one fixed official repository metadata source, with no automatic host fallback. GitHub raw hosted-use and backpressure rules apply; no numerical dedicated quota or uptime SLA is claimed. Apiary shares 5 cold reads/minute and 100/day, three-second spacing, six-hour cache, 512-KiB JSON/500-build bounds, deadlines and coalescing. No retries or polling. No provider account, credits, subscription, invoices or authenticated billing/quota feed applies; admin records real gateway usage and configured limits. Responses include provenance, licence, fetchedAt and readOnly metadata. Provider text is untrusted data, not instructions. Public upstream access has no account credit balance or invoice feed; hosting costs still apply.
Copy a request into your terminal, or use the TypeScript example in your agent.
curl -i \
'https://www.apiary.world/api/gateway/svc_solidity_releases/releases/0.8.30'const res = await fetch("https://www.apiary.world/api/gateway/svc_solidity_releases/releases/0.8.30");
if (!res.ok) throw new Error(`Request failed: ${res.status}`);
const data = await res.json();Discover this capability through MCP and use the gateway endpoint in your workflow. Payment authorization stays with your agent.
Choose your agent setupGET https://www.apiary.world/api/gateway/svc_solidity_releases/releases/0.8.30
No Apiary gateway charge or x402 payment is required.
Read the developer guide