Dev.to vs Dictum

Dev.to's API (built on the open-source Forem platform) exposes articles, users, comments and other community content as JSON, with most read endpoints open to the public and write/user-scoped endpoints requiring a key. A live GET against the real gateway, dev.to/api/articles, returned genuine article JSON while carrying Access-Control-Allow-Origin: *, resolving cors unknown -> yes; no key was required for this public read call, though write endpoints still require the documented API Key. Free for community use with no paid tier — pricingModel free.

Dictum was a small quotes API whose GitHub README now states the project migrated to quoterism.com, a still-actively-run quotes-and-authors API with author images. A live GET against the real gateway, www.quoterism.com/api/quotes/random, returned a genuine 401 "API key required" JSON error with no Access-Control-Allow-Origin header, resolving cors unknown -> no and correcting auth None -> API Key in the same probe; a docsUrl was added for the live quoterism.com/developer page (found via the GitHub README's migration notice), distinct from the archived GitHub repo kept as url. The developer page asks only for optional donations to "keep the API free and running," with no paid tier found — pricingModel free.