For agents
The records are the API: static JSON, stable schema, evidence permalinks. Consult it before adding a Swift dependency.
Zero install: the endpoints below. In Claude Code: the plugin — two pastes. Offline and CI: the CLI.
Endpoints
/api/index.json— start here (endpoint map + schemaVersion)/api/capabilities/{id}.json— the question you're asking: who serves this, where, with what proof/api/packages/{slug}.json— a package's full records/api/taxonomy.json— the capability vocabulary + aliases/api/search-index.json— compact name/alias index
Schema promise: breaking changes bump schemaVersion and the
/api/schemas/… documents; additive fields may appear any time. Treat unknown
fields as forwards-compatible.
Examples
curl -s https://swiftserve.dev/api/capabilities/audio.background-playback.json \
| jq '.packages[] | select(.platforms.macOS.status == "supported") | .packageName'curl -s https://swiftserve.dev/api/index.json | jq '.endpoints'Reading a verdict
supported / unsupported are grounded in parsed source (guards,
availability) at a pinned tag — each evidence item carries a permalink to the
deciding line. unknown means "not verified", never "no". Confidence never
reaches 1.0; anything ≤ 0.3 rests on README-grade evidence only.
CLI
The same dataset ships in the CLI for offline/CI use (install options):
swiftserve capability-check livekit --capability "noise cancellation" --platform macos
swiftserve find --capability audio.recording --platform watchos
swiftserve schema capability-recordExit codes: 0 answered · 1 --expect mismatch (CI gate) · 2 not found.