Core concepts

How Reqistry models the world so decisions are reproducible.

Catalog → Category → API

The catalog holds ~live catalog in live categories (Weather, Finance, AI, …). Each API profile stores normalized fields: slug, name, description, link, documentationUrl, auth, pricing, rateLimit, corsStatus, httpsSupport, OpenAPI availability, warnings, plus live health.

Trust score (0–100, grade A–F)

Eight signals: uptime (24h/7d/30d), response time, docs quality, auth clarity, CORS, pricing clarity, freshness, OpenAPI. Computed by workers, shown with evidence cards — not a black box. See trust scores and evidence.

Health & monitoring

Workers probe URLs with HEAD→GET fallback every ~1h (dead: 1h, recently failed: 2h). Results write api_health_checks + api_current_health (isAlive, statusCode, responseTimeMs, uptime windows, consecutiveFailures). Surfaced on profiles + change feed.

Compare & change feed

Compare 2–4 APIs side-by-side (compare) for auth/pricing/limits/SDKs/latency/CORS/verification. The change feed emits pricing/docs/OpenAPI/health/trust events — the reason to return. Web + push via stacks preferences.

Stacks, bookmarks, folders

Anonymous device auth (DeviceToken) lets you bookmark and folder APIs without signup; link email to sync across devices. Used by web + Android for “My Stack”.

Provider & verification

APIs track field sources (api_field_sources) with verification source (PROVIDER / AUTOMATED_CHECK / IMPORTED / COMMUNITY_REPORT). Claiming is free today; verified badge later adds paid checks (pricing).

MCP

13 read-only tools forwarding to the same REST endpoints. Distribution, not a second catalog. See MCP overview.