Developers

Fred’s web interface needs a signed-in browser session, so it is not something to script against. There are two programmatic surfaces instead: the Fireflies GraphQL API for meeting data, and Fred’s MCP server for calling its tools from an agent. Both authenticate per user and inherit that user’s access — there is no key that reads across an organisation.

GraphQL API

Meetings, transcripts, summaries, action items and users are available from https://api.fireflies.ai/graphql. Authenticate with a Fireflies API key issued from your dashboard, sent as Authorization: Bearer <key>. The full schema and query reference is at docs.fireflies.ai.

MCP server

Fred exposes knowledge-base tools over the Model Context Protocol using the Streamable HTTP transport at /api/mcp. Discovery is public at /.well-known/mcp, which describes the transport and auth scheme. Calls carry service credentials plus an x-user-id header naming the user whose knowledge base is in scope, so the same guarantees as the UI apply: one user, their own data.

Machine-readable descriptions

/openapi.json — OpenAPI 3.1 description of the publicly reachable endpoints, with operation IDs and typed response schemas suitable for function calling.
/llms.txt — what Fred is for, and when an agent should and should not route a request to it.
/api/public/capabilities — the same guidance as JSON, for planners that would rather branch on structure than parse prose.
/sitemap.xml — the public pages on this origin.

Errors and limits

Every endpoint on this origin answers failures as JSON, never an HTML error page: a problem document carrying title, status, a stable code and a resolution hint describing what to do next. Paths that do not exist return a real 404. Rate limits are applied per API key on the GraphQL API and are documented with the endpoints they apply to.

Getting help

Integration questions and API key problems go to [email protected].