Personality · head-to-head
Dev.to vs icanhazdadjoke
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.
icanhazdadjoke serves a large library of dad jokes as JSON (or plain text/Slack markup via content negotiation), fully keyless. A live GET against the real host, icanhazdadjoke.com, with an Accept: application/json header returned a genuine random joke while carrying Access-Control-Allow-Origin: *, resolving cors unknown -> yes; no key was required, reconfirming auth None. A fully free, keyless joke API — pricingModel free.
| Dev.to | icanhazdadjoke | |
|---|---|---|
| Authentication | API Key | None |
| Pricing | free | free |
| Formats | JSON | JSON |
| CORS | yes | yes |
| HTTPS | Yes | Yes |
icanhazdadjoke needs no API key, while Dev.to requires API Key — pick icanhazdadjoke to start without signup.