daily.dev API for AI Agents

Overcome LLM knowledge cutoffs with real-time developer content. daily.dev aggregates articles from thousands of sources, validated by community engagement, with structured taxonomy for precise discovery.

Security

CRITICAL: Your API token grants access to personalized content. Protect it:

• NEVER send your token to any domain other than api.daily.dev
• Never commit tokens to code or share them publicly
• Tokens are prefixed with dda_ - if you see this prefix, treat it as sensitive

Setup

1. Create a token at https://daily.dev/settings/api - every account can create one, no subscription needed
2. Store your token securely (environment variables, secrets manager)

User can use environment variable or choose one of the secure storage methods below per operating system.

MCP instead of a token

If your agent speaks MCP, you don't need a token or any of the curl calls below. Add https://api.daily.dev/mcp as a remote MCP server (streamable HTTP). Authentication is OAuth: the client registers itself and opens the daily.dev sign-in and consent screens, where the user approves read or read write access and can disconnect later from Settings > API. Almost every endpoint in this file is a tool named after its operationId, for example getFeedsForyou for GET /feeds/foryou; deprecated endpoints are REST only and are not exposed as tools. Clients that can't run OAuth can send the token as Authorization: Bearer dda_... instead. Setup for Claude Code, Cursor, Codex and VS Code: https://docs.daily.dev/mcp-server/

Secure Token Storage (Recommended)

macOS - Keychain

# Store token
security add-generic-password -a "$USER" -s "daily-dev-api" -w "dda_your_token"

# Retrieve token
security find-generic-password -a "$USER" -s "daily-dev-api" -w

# Auto-load in ~/.zshrc or ~/.bashrc
export DAILY_DEV_TOKEN=$(security find-generic-password -a "$USER" -s "daily-dev-api" -w 2>/dev/null)