Skip to content
Docs menu

Public and auditor endpoints

The Venom Cloud endpoints that need no Venom key (health, downloads, the docs as markdown and llms.txt) and the auditor API that checks public-mesh daemons.

View .md

A few Venom Cloud endpoints are open to anyone: a health check for load balancers and monitors, stable download links for the CLI and the daemon, and the documentation in forms an agent can read. One more surface, the auditor API, is for the service that checks daemons on the public mesh; it has its own token.

Health: GET /api/status

curl -s https://cloud.usevenom.dev/api/status
{"ok": true, "db": true, "schema": "0113_prompt_experiments", "direct": true, "region": "sin1", "protocol": "1.0"}
Field Meaning
ok, db the database answered; the status is 200, else 503 with both false
schema the newest applied database migration (its file name without .sql)
direct the direct path (307 plus a ticket to a daemon) is on: the deployment has signing keys
region the serving region (VERCEL_REGION, else VENOM_CLOUD_REGION, else sin1)
protocol the mesh protocol version daemons speak

No auth, nothing about any org, cache-control: no-store. Point uptime checks here.

Downloads

Stable links that always point at the release the site offers (the newest published one), so scripts and install docs never need a version number. Each answers 302 to the asset on the public releases repository, cached for 5 minutes; an unknown name is 404. Nothing is logged.

Route Redirects to
GET /download/{platform} the venom CLI archive for macos-arm64, macos-x64, linux-x64, linux-arm64 or windows-x64 (beta)
GET /download/sha256sums the CLI release's SHA256SUMS
GET /download/daemon/{platform} the Venom daemon for a platform, or a Mac's app zip (macos-arm64-app, macos-x64-app)
GET /download/daemon/sha256sums the daemon release's SHA256SUMS
curl -fsSLO -L https://cloud.usevenom.dev/download/linux-x64
curl -fsSL -L https://cloud.usevenom.dev/download/sha256sums

Check the archive against SHA256SUMS before you install it. The install guide has the full steps.

The docs, for agents

Every docs page is also served as markdown, and the whole site as llms.txt files, so an agent can read the docs without parsing HTML.

Route What it serves
GET /docs/<section>.md, GET /docs/<section>/<slug>.md the page's markdown with its frontmatter, links made absolute
GET /docs/llms.txt the llmstxt.org index: one - [title](url.md): description line per page, by section
GET /docs/llms-full.txt every page's markdown, in reading order
GET /docs/search.json the search index the site's search box reads
GET /docs/sitemap.xml every docs URL

The .md URLs are rewritten to an internal /docs-md/<path> route, which is not reachable directly. All of these are built with the site, so they change only with a deploy.

curl -s https://cloud.usevenom.dev/docs/llms.txt | grep -i "cloud"
curl -s https://cloud.usevenom.dev/docs/cloud/api-overview.md

Auditor API

On the public mesh anyone can host a daemon, so Venom checks their work: an auditor replays sampled public jobs against a reference model and sends canary requests. That service (venom-auditor) talks to the cloud through /api/audit/v1/* with Authorization: Bearer <VENOM_CLOUD_AUDITOR_TOKEN>. An operator running their own deployment sets the token (32 characters or more); without it every route answers 503 auditor_not_configured. Org keys never reach these routes.

Route What it does
GET /api/audit/v1/registry the registry entries (model, tolerance, allowed mismatches) audits replay against
POST /api/audit/v1/claim?limit=N lease up to N pending audits for 10 minutes: the job, its receipt, the request and the witnessed output
POST /api/audit/v1/{audit_id}/renew extend a held lease to 10 minutes from now (renew every 4 minutes during a long replay)
POST /api/audit/v1/{audit_id}/verdict the verdict for the audit's current run: pass, fail or inconclusive, with checks and up to 32 evidence entries
POST /api/audit/v1/canary run a canary request on one daemon through the normal queue and relay its answer as a client would see it
GET /api/audit/v1/daemons every public daemon with its trust state, models and last day's public jobs and canaries

A verdict or renewal for an audit that is not leased, already decided, or at another run answers 409; an unknown audit 404. The full protocol, including what the auditor checks and how a daemon is quarantined, is in docs/public-mesh.md §7.