Public endpoints

Let anyone read one endpoint with no account, over REST or a guest MCP server, and never a picture.

An administrator can make one endpoint public. Anyone can then read its values, how surely each was read, since when, and its last day, with no token. Nobody sees its pictures, crops or anything else in your workspace.

Try it

Chamber A at NASA’s Webb test chamber is public. Its camera is a looped public-domain NASA recording.

Read it
Connect Claude Code to it

Then ask your agent whether Chamber A is sealed.

Make an endpoint public

Publish loading_bay as loading-bay

You should see the endpoint’s name, its slug and the url anyone reads. Only an administrator, or an operator token, can publish or unpublish. A slug is 1 to 40 lowercase letters, digits and hyphens, and is unique across Dialect: one taken answers 409.

RouteDoes
GET /v1/endpoints/{name}/publicWhether it is public, and as what
PUT /v1/endpoints/{name}/publicMakes it public, or changes its slug
DELETE /v1/endpoints/{name}/publicMakes it private again, at once

What anyone gets

RouteAnswers
GET /v1/publicEvery public endpoint: endpoint (its slug), title, url
GET /v1/public/{slug}title, fresh, checked_at, each field’s asks, value, sure, unsure_why, since, then last_24h summed and the latest changes

An endpoint that isn’t public, or doesn’t exist, is 404. Answers carry Access-Control-Allow-Origin: *, so a browser on any site can read them, and Cache-Control: public, max-age=5. Each address may read 120 times a minute; past that it gets 429 with Retry-After.

The guest MCP server, https://api.dialectlayer.com/mcp/public, needs no account and has four read-only tools: dialect_endpoints, dialect_read_endpoint, dialect_summary and dialect_changes. Each takes the slug as name. It can’t set up, look, write or reach any endpoint that isn’t public.