4chan vs Blogger

4chan's API serves the same read-only board and thread data every page renders — board lists, catalogs, threads, and posts — as plain JSON from the dedicated a.4cdn.org host, with no registration, key, or authentication of any kind required. Media referenced by posts is served from the sibling i.4cdn.org host, and the project's own GitHub repository (4chan/4chan-API) hosts the reference client and doubles as the canonical documentation, including the rule to cap requests at one per second. Cross-origin use from a browser is limited in practice: both the docs and a live probe confirm the API's CORS policy only allows requests originating from 4chan's own board pages, so a third-party site must proxy requests server-side rather than call it directly from client-side JavaScript.

Blogger API v3 is Google's REST/JSON interface for its blogging platform, letting apps retrieve and manage blogs, posts, comments, and pages. Public data can be read with a plain API key, but writing content or touching private data requires a full OAuth 2.0 authorization flow. The docs still list the deprecated v1.0 and v2.0 protocol guides alongside the current v3.0 reference, reflecting a mature, low-churn API that hasn't needed a v4.