DEV Community publishes a ChatGPT-plugin-shaped OpenAPI spec exposing a single article search endpoint at /api/articles/search. It lets a language model query DEV's article corpus by keyword, tag, or username and recommend relevant resources back to a user. Because there is exactly one operation, this spec is best understood as a focused recommendation tool rather than a full content management surface - for write operations and the rest of DEV's content model, use the Forem API V1 (dev.to main) instead.
1 endpointsThe Forem API V1 powers DEV Community (dev.to) and other Forem-based developer communities. Its 58 endpoints cover articles, comments, reactions, tags, follows, organizations, pages, podcast episodes, billboards, segments, and admin operations such as suspending or marking users as trusted. Public reads work anonymously, while write operations and reads of personal content require the api-key request header issued from a user's DEV settings page. Use it to publish technical content programmatically, build dashboards over your own articles, or moderate a Forem instance from external tooling.
58 endpointsStep 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.