Install Jentic One Beta

Connect the daily.dev Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the daily.dev Public API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdaily.dev%2Fdaily" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdaily.dev%2Fdaily" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with daily.dev Public API.

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

GET STARTED

Start building with daily.dev Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use daily.dev Public API for, with concrete tasks.

★ 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.

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.

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.

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.

Search posts for a keyword and return the top matching sources

Key Endpoints

67 endpoints — the daily.

METHOD

PATH

DESCRIPTION

GET

/feeds/foryou

Personalized for-you feed

GET

/feeds/popular

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using daily.dev Public API through Jentic.

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.

daily.dev Public API

AI ReadinessFoundational (C+)58/100

See full scorecard

Official vendor OpenAPI document · agent-readySocial MediaSocial Managementbearer, oauth267 EndpointsREST

For 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.

Use for: Get my personalized for-you developer feed, Search posts about a specific technology, Bookmark a post to a named list, Create a custom feed filtered by tags

Not supported: 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.

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

89%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

39%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

91%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A-Signals: 1

75%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

61%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the daily.dev Public API to your agent

Capabilities

Start building with daily.dev Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

daily.dev Public API

Jentic AI Readiness Score

daily.dev Public API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness