Google Analytics vs Pick an Agency

The Google Analytics 4 Data API (`analyticsdata.googleapis.com/v1beta`) lets applications pull custom reports of metrics, dimensions, and audience segments out of a GA4 property, complementing a separate Admin API used to manage properties, streams, and access. It requires a Google OAuth 2.0 bearer token, confirmed live via a `WWW-Authenticate: Bearer realm="https://accounts.google.com/"` challenge on an unauthenticated `runReport` call, and the same request repeated with an Origin header echoed `access-control-allow-origin` back, resolving CORS support from unknown to yes. The core Data API is free to call within Google's standard quotas, with Google Analytics 360 offered as a paid enterprise tier for higher limits and additional features.

Pick an Agency runs a free, no-signup REST + MCP API over its directory of 47,000+ verified marketing agencies, publishing a machine-readable OpenAPI spec at `/api/v1/openapi.json` alongside `/search`, `/agencies/{slug}`, and `/match` endpoints for shortlisting agencies by service, location, and rating. An OPTIONS preflight against `/api/v1/search` confirms the advertised open CORS policy (`access-control-allow-origin: *`), and no endpoint ever demanded a key or returned an auth challenge, reconfirming the stored 'None' auth. The three data-fetching GET endpoints themselves consistently timed out from this sandbox's egress on every attempt — the spec and homepage load fine, so their live JSON payloads could not be directly confirmed this run, though nothing points to the API being down.