A keyed, versioned REST API over the whole catalog — for apps that need Arab screen data with provenance.
https://api.menascreendb.com/api/v1
Authenticate with a bearer key (Authorization: Bearer msdb_live_…). Errors follow RFC 7807; pagination is cursor-based; every response carries an X-MSDB-API version header plus X-RateLimit-Limit/X-RateLimit-Remaining (per-key read and write budgets; a 429 includes Retry-After). Keys carry scopes — read endpoints need read:public; write endpoints list their scope below. Everything written through the API lands in the unverified lane with provenance and is publicly visible with its trust status — being first never bypasses being honest. TMDB-sourced fields are attributed per TMDB terms.
/api/v1/search?q=/api/v1/autocomplete?q=/api/v1/discover/api/v1/projects/{id}/api/v1/projects/{id}/credits/api/v1/projects/{id}/artwork/api/v1/projects/{id}/availability/api/v1/people/{id}/api/v1/people/{id}/credits/api/v1/companies/{id}/api/v1/external-ids/resolve/api/v1/search/semanticread:embeddings/api/v1/projects/{id}/embeddingread:embeddings/api/v1/people/{id}/embeddingread:embeddings/api/v1/meta/coverage/api/v1/meta/freshness/api/v1/meta/attribution/api/v1/health/api/v1/productionswrite:productions/api/v1/creditswrite:credits/api/v1/claimswrite:claims/api/v1/gap-ticketswrite:gap_tickets/api/v1/artwork/upload-intentwrite:artworkAPI keys are issued to licensed consumers. To request access, contact corrections@menascreendb.com. Read more about sourcing and attribution on the About page.