canonical: https://jentic.com/apis/dev.to/dev-to-chatgpt

# Dev To DEV Community ChatGPT Plugin API

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.

## For AI agents

Search DEV Community articles by keyword, tag, or username through a single GET /api/articles/search endpoint, suitable as an LLM tool for content recommendation.

## Scope

Does not read full article bodies, list comments, or perform any write operation - use for searching DEV Community articles only.

## Capabilities

- Search DEV Community articles by free-text keyword via GET /api/articles/search
- Filter article results by tag, username, or other supported query parameters in /api/articles/search
- Recommend DEV articles to a user based on a topical prompt with a single tool call
- Retrieve article metadata (title, url, tags) suitable for embedding in an LLM response
- Use anonymously without an API key for public read-only article discovery

## Use cases

### LLM article recommender

An LLM can call GET /api/articles/search to recommend DEV Community articles that match a user's question or interest. The endpoint accepts free-text and filters such as tag and username, and returns enough metadata for the model to cite article titles and URLs in its answer. Because the endpoint is anonymous and read-only, there is no credential handling for this specific operation.

Example prompt: GET /api/articles/search?q=rust+async+tokio and return the top 3 results with title and URL to the user.

### Tag-based content discovery

Use the search endpoint with a tag filter to surface recent DEV articles in a topic area, useful for newsletter curation, learning tracks, or in-app content modules. Pair the results with the Forem main API if you need to fetch full bodies, comment counts, or write reactions; this plugin spec only covers the search itself.

Example prompt: GET /api/articles/search?tag=javascript&q=performance and produce a curated list of 5 articles for a weekly newsletter.

### Agent-driven recommendation tool

An AI agent can register the DEV search operation as a single tool through Jentic and call it whenever a user asks for technical reading material. Jentic returns the operation schema and executes the request, so the agent does not need to maintain its own DEV integration code path or worry about endpoint format changes.

Example prompt: Through Jentic, search 'search dev.to articles', load the dev.to chatgpt /api/articles/search operation, and execute with the user's topic to return ranked article suggestions.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /api/articles/search | Search DEV Community articles by keyword, tag, or username |

## Key resources

- **Article Search** — Single search endpoint over DEV articles via GET /api/articles/search with keyword, tag, and username parameters.

## Why Jentic

- **Setup:** Wiring the DEV Community article search by hand means building the GET /api/articles/search call and parsing its query parameters and response yourself. Through Jentic you install once, import the DEV Community ChatGPT Plugin API from the API Directory, and your agent calls it, and since the search endpoint is anonymous there is no credential to configure.
- **Permission scoping:** The DEV article search exposes a single read-only operation, so you limit the agent to that search call: it can find published articles and has no ability to read full bodies, list comments, or write.
- **Credential handling:** The DEV article search endpoint is anonymous, so no secret is held. Jentic still routes the call through your own instance so the agent's own keys and identity stay isolated from the upstream request and never enter its prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'find DEV articles about React', and Jentic returns the dev.to search operation with its query parameter schema so the agent calls the right endpoint without browsing the docs.

## Related APIs

- **Forem API V1** — Full DEV/Forem API covering articles, comments, users, and write operations.
- **GitHub REST API** — Search and read code repositories alongside DEV articles.
- **Product Hunt** — Community-curated product launches and discussions.

## FAQ

### What does the DEV Community ChatGPT API actually do?

It exposes a single endpoint, GET /api/articles/search, which lets an LLM search DEV Community articles by keyword, tag, or username. The response is metadata suitable for citing article titles and URLs back to a user. For broader DEV functionality such as reading full articles or writing posts, use the Forem API V1 at dev.to main.

### What authentication does the DEV ChatGPT plugin API require?

The /api/articles/search endpoint in this spec is anonymous and read-only - no API key is required. Through Jentic, the call goes out from a Jentic-managed identity, so no credential is provisioned or required for this operation.

### Can I write or publish articles with this DEV API?

No. This spec is read-only and limited to /api/articles/search. To create or update DEV articles, use the Forem API V1 (vendor dev.to, slug main), which exposes write operations on /api/articles and authenticates with the api-key header.

### How do I recommend DEV articles to a user through Jentic?

Search Jentic for 'search dev.to articles', load the dev.to chatgpt /api/articles/search operation, and execute it with the user's query, optionally adding tag or username filters. Render the returned titles and URLs back into the agent's response.

### What are the rate limits for the DEV article search endpoint?

DEV does not publish formal rate limits in the spec. As with any public anonymous endpoint, expect per-IP throttling and treat HTTP 429 as a signal to back off. For sustained or higher-throughput discovery, use the authenticated Forem API V1 instead.

### Can I limit what my agent is allowed to do with the DEV Community ChatGPT Plugin API?

Yes. Jentic One runs self-hosted, so your own rules decide which operations and credentials the agent may use, and this API exposes just one read-only operation, GET /api/articles/search. You can scope the agent to that single search call, letting it find published DEV Community articles by keyword, tag, or username while giving it no way to read full article bodies, list comments, or write posts. Anything beyond article search stays off limits because you never grant it.