Dev.to vs Medium

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.

Medium's REST API lets a registered integration read a user's profile and publish posts on their behalf, gated behind an OAuth-issued integration token (Medium stopped issuing new integration tokens in 2023, but existing tokens still authenticate). A live GET against the real gateway, api.medium.com/v1/me, returned a genuine 401 "An access token is required" JSON error while carrying Access-Control-Allow-Origin: *, resolving cors unknown -> yes and reconfirming OAuth auth in the same probe. No paid tier ever existed for the API itself — pricingModel free.