Gmail vs Pick an Agency

The Gmail API gives OAuth-scoped programmatic access to a user's mailbox: reading, searching, sending, and organizing messages, threads, labels, and drafts, with message bodies transported as base64url-encoded MIME inside JSON. 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 request, and unlike most server-side email APIs it explicitly supports cross-origin browser calls, echoing the request Origin on both a GET and an OPTIONS preflight.

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.