Docs / Hosts

Stable

Validate host compatibility

Use the validator before a host claims optional compatibility metadata or asks Atmosphere to show support badges.

Validate a published manifest by host or URL.Validate a local JSON file during development.Treat warnings as compatibility cleanup and errors as badge blockers.Passing conformance can unlock directory signals; it does not delegate account-management authority to Atmosphere.

CLI

Run the local validator

SH
deno task host:conformance host.example
deno task host:conformance host.example --json
deno task host:conformance host.example --write
Badge policy

Atmosphere only shows a compatibility badge after the manifest, account route, and PDS health checks pass. Stored results expire after seven days. Public listing is separate: a host must be reachable and intentionally public, with a short grace period for temporarily inactive claimed hosts.

Use the public validator API

GET/api/hosts/dashboard/validate?host=host.example

Fetches the host’s well-known manifest and validates it against the v0.1 contract.

POST/api/hosts/dashboard/validate?host=host.example

Validates the JSON request body directly. Useful for local previews, CI, and docs examples.

SH
curl -X POST \
  "https://atmosphereaccount.com/api/hosts/dashboard/validate?host=host.example" \
  -H "content-type: application/json" \
  --data-binary @manifest.json

Validation result shape

JSON
{
  "ok": false,
  "manifest": null,
  "issues": [
    {
      "severity": "error",
      "path": "$.capabilities.connectedApps.state",
      "message": "Capability state must be supported, host_owned, planned, or unknown."
    }
  ]
}
On this page