Countly vs Creative Commons Catalog

Countly is an open-source product analytics platform you self-host (or run as their managed cloud), ingesting events over a REST Data API keyed by a per-app `app_key` rather than a private secret — a live unauthenticated POST to a running Countly server (try.count.ly/o) confirmed the endpoint only demands `app_key`, returning a `missing_api_key` JSON error otherwise. The Community Edition is free and self-hostable under an AGPLv3-derived license; Countly also sells a paid Enterprise Edition with SSO, extra data sources, and dedicated support.

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.