Creative Commons Catalog vs Metabase

Creative Commons's search catalog was handed off to WordPress.org and relaunched as Openverse; the old `api.creativecommons.engineering` host now 301-redirects to the current `api.openverse.org`. A live unauthenticated GET against `api.openverse.org/v1/images/` returned a 200 JSON result set with `Access-Control-Allow-Origin: *`, confirming keyless anonymous search still works today (rate-limited to 200 requests/day per IP), with an optional `/v1/auth_tokens/register/` OAuth2 client-registration endpoint (confirmed live, returning a 400 validation error rather than 404) for higher limits. The catalog itself and every indexed work are free to use under their respective open licenses.

Metabase is a self-hosted (or Metabase Cloud) open-source BI tool whose REST API is documented via an interactive OpenAPI/Scalar reference at `/docs/latest/api`; current docs describe generating an `x-api-key` from Admin settings for programmatic access, correcting auth from "None" to "API Key" (the older session-cookie login flow still exists but keyed API access is now the documented path). Its own `MB_DISABLE_CORS_ON_LOCALHOST` config option (default `false`) confirms the server sends CORS headers by default, consistent with cors "yes". The core server is free and open-source to self-host, with paid Pro, Enterprise, and hosted Cloud tiers layered on top.