DEV Community
DEV Community (DEV.to) is a developer community platform built on the open-source Forem software. It provides a REST API for managing articles, comments, user profiles, organizations, podcast episodes, and accessing published developer content. The API supports creating and updating posts, retrieving community content by tag or author, managing reactions and reading lists, and administering organizations. Authentication uses an API key passed via the api-key header, with public read access available without authentication.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles DEV Community the way a machine reads it — 201 machine-readable artifacts across 19 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — DEV Community scores 47.7/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile DEV Community
Each block below is one kind of artifact we hold for DEV Community. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 19
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
DEV Community agent_sessions API
The agent_sessions API from DEV Community — 2 operation(s) for agent_sessions.
DEV Community articles API
The articles API from DEV Community — 22 operation(s) for articles.
DEV Community billboards API
The billboards API from DEV Community — 3 operation(s) for billboards.
DEV Community comments API
The comments API from DEV Community — 4 operation(s) for comments.
DEV Community display ads API
The display ads API from DEV Community — 3 operation(s) for display ads.
DEV Community followed_tags API
The followed_tags API from DEV Community — 2 operation(s) for followed_tags.
DEV Community followers API
The followers API from DEV Community — 2 operation(s) for followers.
DEV Community organizations API
The organizations API from DEV Community — 8 operation(s) for organizations.
DEV Community pages API
The pages API from DEV Community — 4 operation(s) for pages.
DEV Community podcast_episodes API
The podcast_episodes API from DEV Community — 2 operation(s) for podcast_episodes.
DEV Community profile images API
The profile images API from DEV Community — 2 operation(s) for profile images.
DEV Community reactions API
The reactions API from DEV Community — 4 operation(s) for reactions.
DEV Community readinglist API
The readinglist API from DEV Community — 2 operation(s) for readinglist.
DEV Community segments API
The segments API from DEV Community — 5 operation(s) for segments.
DEV Community surveys API
The surveys API from DEV Community — 4 operation(s) for surveys.
DEV Community tags API
The tags API from DEV Community — 4 operation(s) for tags.
DEV Community trends API
The trends API from DEV Community — 3 operation(s) for trends.
DEV Community users API
The users API from DEV Community — 23 operation(s) for users.
DEV Community videos API
The videos API from DEV Community — 2 operation(s) for videos.
Scroll within the panel for all 19 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Devto Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Devto Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Devto Finops
FINOPSSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
DEV Community API Rules
SPECTRALJSON Schema 30
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AgentSessionIndex
JSON SCHEMAAgentSessionShow
JSON SCHEMAArticle
JSON SCHEMAArticleFlareTag
JSON SCHEMAArticleIndex
JSON SCHEMABillboard
JSON SCHEMAComment
JSON SCHEMAExtendedUser
JSON SCHEMAFollowedTag
JSON SCHEMAMyUser
JSON SCHEMAOrganization
JSON SCHEMAPage
JSON SCHEMAPodcastEpisodeIndex
JSON SCHEMAPoll
JSON SCHEMAPollOption
JSON SCHEMAPollTextResponse
JSON SCHEMAPollVote
JSON SCHEMAProfileImage
JSON SCHEMASegment
JSON SCHEMASegmentUserIds
JSON SCHEMASharedOrganization
JSON SCHEMASharedPodcast
JSON SCHEMASharedUser
JSON SCHEMASurvey
JSON SCHEMASurveyWithPolls
JSON SCHEMATag
JSON SCHEMATrend
JSON SCHEMAUser
JSON SCHEMAUserInviteParam
JSON SCHEMAVideoArticle
JSON SCHEMAScroll within the panel for all 30 ·
Examples 144
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Createarticle Response 201
EXAMPLECreatearticle Response 401
EXAMPLECreatearticle Response 422
EXAMPLECreatesegment Response 201
EXAMPLECreatesegment Response 401
EXAMPLEDeletesegment Response 200
EXAMPLEDeletesegment Response 401
EXAMPLEDeletesegment Response 404
EXAMPLEDeletesegment Response 409
EXAMPLEGetarticlebyid Response 200
EXAMPLEGetarticlebyid Response 404
EXAMPLEGetarticles Response 200
EXAMPLEGetcommentbyid Response 200
EXAMPLEGetcommentbyid Response 404
EXAMPLEGetfollowedtags Response 200
EXAMPLEGetfollowedtags Response 401
EXAMPLEGetfollowers Response 200
EXAMPLEGetfollowers Response 401
EXAMPLEGetorgarticles Response 200
EXAMPLEGetorgarticles Response 404
EXAMPLEGetorgusers Response 200
EXAMPLEGetorgusers Response 404
EXAMPLEGetorganization Response 200
EXAMPLEGetorganization Response 404
EXAMPLEGetprofileimage Response 200
EXAMPLEGetprofileimage Response 404
EXAMPLEGetreadinglist Response 401
EXAMPLEGetsegment Response 200
EXAMPLEGetsegment Response 401
EXAMPLEGetsegment Response 404
EXAMPLEGetsegments Response 200
EXAMPLEGetsegments Response 401
EXAMPLEGetsurveys Response 200
EXAMPLEGetsurveys Response 401
EXAMPLEGettags Response 200
EXAMPLEGettrend Response 200
EXAMPLEGettrend Response 404
EXAMPLEGettrends Response 200
EXAMPLEGetuserarticles Response 401
EXAMPLEGetuserme Response 200
EXAMPLEGetuserme Response 401
EXAMPLEGet_Api_Pages Response 200
EXAMPLELimituser Response 401
EXAMPLELimituser Response 404
EXAMPLEPost_Api_Pages Response 200
EXAMPLEPost_Api_Pages Response 401
EXAMPLEPost_Api_Pages Response 422
EXAMPLESpamuser Response 401
EXAMPLESpamuser Response 404
EXAMPLESuspenduser Response 401
EXAMPLESuspenduser Response 404
EXAMPLETrustuser Response 401
EXAMPLETrustuser Response 404
EXAMPLEUnlimituser Response 401
EXAMPLEUnlimituser Response 404
EXAMPLEUnspamuser Response 401
EXAMPLEUnspamuser Response 404
EXAMPLEUntrustuser Response 401
EXAMPLEUntrustuser Response 404
EXAMPLEUnpublishuser Response 401
EXAMPLEUnpublishuser Response 404
EXAMPLEUpdatearticle Response 200
EXAMPLEUpdatearticle Response 401
EXAMPLEUpdatearticle Response 404
EXAMPLEUpdatearticle Response 422
EXAMPLEVideos Response 200
EXAMPLEScroll within the panel for all 144 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for DEV Community — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/devto · machine-readable index on apis.io