# FreeDailyPro API & MCP

> A REST API and MCP (Model Context Protocol) server for a subset of FreeDailyPro's 200+ free browser tools -- covers PDF/document, text, security, converter, calculator, and business-document tools. Video, audio, and image-editing tools are browser-only right now and are NOT available through this API or MCP -- don't assume a route exists for them.

## Base URL
https://api.freedailypro.com

## Authentication
Header: X-API-Key: <your key>
Free tier: 20,000 calls/month, one key, one shared quota across every endpoint.
Get a free key: sign in at https://www.freedailypro.com/developers and click "Generate API Key" -- takes under a minute, no credit card.
Regenerating your key immediately revokes the old one everywhere it's used -- don't regenerate a key you already have working somewhere just to "get a fresh one" for a quick test; the existing key already works.

## Try without a key first
POST /v1/text/word-count, POST /v1/text/slug, and POST /v1/text/case-convert work with NO key at all (IP rate-limited, 10 requests/hour) -- a real way to confirm the API works before generating a key.

## Machine-readable coverage
GET https://api.freedailypro.com/openapi.json -- the real, generated OpenAPI 3.0 spec (currently ~139 paths). This is the actual, current source of truth for what's callable -- if a path isn't in this spec, it doesn't exist, regardless of what any other page or listing (Postman, RapidAPI, MCP registry) might separately say.

## Interactive docs
https://api.freedailypro.com/docs -- Swagger UI, live against the real API, browsable by category.

## MCP (for AI agents)
Endpoint: POST https://api.freedailypro.com/mcp
Same X-API-Key header as REST. Send a standard MCP tools/list request to get the current, real tool list (JSON-RPC over SSE) -- tool names/descriptions are generated from the same source as the OpenAPI spec, so the two stay in sync.

## Unknown routes
A path that doesn't exist returns a real 404, even without a key -- a 401 specifically means the route is real but your key is missing or invalid, never "maybe this doesn't exist."

## Privacy / trust model
This is a genuinely different trust model from the site's own browser tools (which process files locally and never leave the device) -- calling this API sends your data to our server for processing. Files aren't stored after a response is returned, but they are transmitted, which the browser-based tools never do.