canonical: https://jentic.com/apis/daily.dev/daily # daily.dev Public API The daily.dev Public API gives agents and automations programmatic access to the daily.dev developer content platform. It returns personalized feeds (for-you, popular, and most discussed), searches posts, tags, and sources, and manages bookmarks and bookmark lists. It also builds custom feeds with advanced filters, follows or blocks tags and sources, reads post comments and notifications, and updates your profile, tech stack, and work experiences. Free accounts get a monthly request quota that Plus raises. ## For AI agents Read personalized developer news feeds, search posts and sources, manage bookmarks and custom feeds, and tune follows on daily.dev. Agents can also read notifications and update the user's profile. ## Scope Does not host or publish your own articles, send direct messages, or manage billing. Use for reading and curating the daily.dev developer feed only. ## Capabilities - Fetch personalized developer feeds: for-you, popular, and most discussed posts - Search posts, tags, and sources across the daily.dev content graph - Create and organize bookmarks and bookmark lists - Build and manage custom feeds with advanced filtering settings - Follow or block tags and sources to tune the feed - Read and update your profile, tech stack, and work experiences - Retrieve notifications and mark them read ## Use cases ### AI Agent News Briefing An AI agent connected through Jentic can pull the popular or for-you developer feed and summarise what matters that day. The agent searches for the operation it needs, daily.dev returns the matching endpoint and input schema, and the agent calls it with a stored token. This turns a personal feed into an automated morning briefing without a human opening the app. Example prompt: Fetch the popular developer feed and summarise the top five posts ### Personalized Feed Curation Create a custom feed and shape it by following or blocking specific tags and sources, then adjust its advanced settings. This lets an automation maintain a focused reading list for a team or topic without manual clicking. Example prompt: Create a custom feed and follow two tags so they appear in it ### Bookmark Management Save posts as bookmarks and organize them into named lists, then search within saved items. An agent can file interesting posts for later review and keep lists tidy on the user's behalf. Example prompt: Bookmark a post and add it to a named bookmark list ### Developer Content Search Search across posts, tags, and sources to find coverage of a specific technology or author. This backs research tasks that need the latest developer discussion on a topic rather than a static feed. Example prompt: Search posts for a keyword and return the top matching sources ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/feeds/foryou` | Personalized for-you feed | | GET | `/feeds/popular` | Popular posts feed | | GET | `/search/posts` | Search posts | | POST | `/bookmarks/` | Create a bookmark | | POST | `/feeds/custom/` | Create a custom feed | | POST | `/feeds/filters/tags/follow` | Follow tags | | GET | `/notifications/` | List notifications | | GET | `/profile/` | Get the current profile | ## Key resources - **Feeds** — Personalized, popular, discussed, tag, and source feeds - **Search** — Search posts, tags, and sources - **Bookmarks** — Bookmarks and bookmark lists - **Custom Feeds** — Custom feeds with advanced filter settings - **Profile** — Profile, tech stack, experiences, and notifications ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 58 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 72 / 100 - Developer Experience & Jentic Compatibility: 62 / 100 - AI-Readiness & Agent Experience: 35 / 100 - Agent Usability: 91 / 100 - Security: 75 / 100 - AI Discoverability: 61 / 100 - **View full report:** https://jentic.com/apis/daily.dev/daily/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring daily.dev by hand means handling a personal access token or an OAuth 2.0 authorization-code flow, scope selection, and the free-versus-Plus quota. Through Jentic you install once, import daily.dev from the API Directory, store your token once, and your agent calls it. - **Permission scoping:** daily.dev's write operations (posting bookmarks, creating custom feeds, following or blocking sources, updating your profile) are separate from its read endpoints, so a rule can hold your agent to the reads it needs. You choose the operations it may call, so changing your follows or profile is not included unless you add it. - **Credential handling:** Your daily.dev token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'get my developer feed' or 'search posts about a technology', and Jentic returns the matching daily.dev operation with its input schema so the agent calls the right endpoint without reading the docs. ## Related APIs - **DEV Community (Forem)** — Read and publish developer articles on the DEV platform. - **Reddit** — Read posts and comments from developer subreddits and communities. - **Product Hunt** — Discover newly launched developer and tech products. - **NewsAPI** — Search mainstream news headlines across many publishers. ## FAQ ### What authentication does the daily.dev Public API use? The daily.dev Public API accepts a personal access token or an OAuth 2.0 access token per its OpenAPI spec, both sent as a Bearer credential in the Authorization header, and OAuth scopes separate read from write. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's prompt or logs. ### Can I build a custom feed with the daily.dev Public API? Yes. Create a custom feed, then follow or block tags and sources and adjust its advanced settings to shape what appears. Note that bookmark folders and clickbait-shielded titles require a Plus account. ### Is there a daily.dev MCP server? You don't need an MCP server to give your agent daily.dev. Jentic connects it directly from the API Directory: import the API, store your token once, and your agent calls the feed, search, and bookmark endpoints it needs. ### Can I limit what my agent is allowed to do with the daily.dev Public API? Yes. Write a rule that allows only the feed and search read operations, so a briefing agent can read posts while your bookmarks, follows, and profile stay unchanged, and every call it makes is logged. ### What are the rate limits for the daily.dev Public API? The OpenAPI spec does not publish specific request limits, but daily.dev gives free accounts a monthly request quota and raises it on Plus. Check daily.dev for the quota that applies to your account. ### How do I read my developer feed with the daily.dev Public API through Jentic? Search Jentic for an intent like 'get my developer feed', and it returns the daily.dev for-you feed operation with its input schema so your agent calls it. Your stored token is injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.