# Eodly > Eodly sends founders, CEOs, and team leads one sourced end-of-day report every evening: what got done, who is silent, who is slipping. It captures what a team actually did across Slack, Telegram, and Discord check-ins plus GitHub and Linear activity, and gates KOL/partnership payouts on proof of delivery. Eodly exposes a read-only REST API so AI agents can fetch a workspace's end-of-day reports and team roster. Authentication is an organization-scoped API key sent as a Bearer token (`Authorization: Bearer eodly_sk_...`), with read-only scopes (`reports:read`, `team:read`). Keys are created and revoked in the app under Settings, on the Developer tab. ## Developer resources - [Developer & API documentation](https://eodly.io/developers): Overview, base URL, scopes, endpoints, and code examples (curl, JavaScript, Python). - [Agent authentication guide](https://eodly.io/developers#authentication): Step by step on how an AI agent obtains and uses an API token. - [OpenAPI specification](https://eodly.io/openapi.json): Machine-readable OpenAPI 3.1 description of the Eodly API, including the Bearer security scheme and scopes. - [Eodly MCP server setup](https://eodly.io/docs/mcp-server): How to connect Eodly to Claude, Cursor or any MCP client: sign in with Eodly (OAuth) at `https://eodly.io/mcp`, or use an API key with the hosted endpoint or the npm package, with the client config, the four tools and the scope each one needs. - [Connect Eodly to Claude](https://eodly.io/blog/connect-eodly-to-claude): Add `https://eodly.io/mcp` as a custom connector in Claude, sign in with Eodly and approve; read-only, every plan, disconnect under Settings > Developer > Connected apps. - [MCP server card](https://eodly.io/.well-known/mcp/server-card.json): Describes the remote MCP endpoint `https://eodly.io/api/mcp` (Streamable HTTP, POST only, so a GET returns 405) for Claude and Cursor, or install the stdio package with `npx @eodly/mcp` ([@eodly/mcp on npm](https://www.npmjs.com/package/@eodly/mcp)). Supports MCP Apps: the report tools render an interactive card via the `ui://eodly/report.html` resource. - [Agent authentication guide (markdown)](https://eodly.io/auth.md): The same guidance as a plain markdown file, for agents that prefer not to parse HTML. - [Command line tool](https://github.com/layergen/eodly-cli): Read reports and the roster from a terminal or a script. Run it with `npx github:layergen/eodly-cli reports`. Commands: `whoami`, `reports`, `report `, `team`, each with `--json` for piping to jq. Exit codes: 0 success, 1 request failure, 2 usage error. ## Machine-readable discovery files - [Agentic resource catalog](https://eodly.io/.well-known/ai-catalog.json): ARD 1.0 catalog listing every Eodly agentic surface (MCP server, REST API, agent skills, docs) in one file. - [MCP server card](https://eodly.io/.well-known/mcp/server-card.json): Transport, protocol versions, capabilities, authentication, and the full tool list for the Eodly MCP server. - [Agent skills index](https://eodly.io/.well-known/agent-skills/index.json): Published Eodly agent skills, with a sha256 for each SKILL.md. - [Sitemap](https://eodly.io/sitemap.xml): Every public Eodly page. ## API endpoints - Base URL: `https://eodly.io/api/v1` - [Identify a key](https://eodly.io/api/v1/me): GET /api/v1/me returns the key's organization and scopes. - [List reports](https://eodly.io/api/v1/reports): GET /api/v1/reports returns recent end-of-day report summaries (scope: reports:read). - [Get a report](https://eodly.io/api/v1/reports/{id}): GET /api/v1/reports/{id} returns one full report (scope: reports:read). - [Team roster](https://eodly.io/api/v1/team): GET /api/v1/team returns the team roster (scope: team:read). ## Content - [Blog](https://eodly.io/blog): Notes on running mixed teams, accountability without surveillance, and sourced end-of-day reporting. - [Resources](https://eodly.io/resources): Guides, FAQ, and exactly what Eodly reads. - [FAQ](https://eodly.io/faq): What Eodly is, what it connects to, how check-ins work, and how it handles data. - [Discord standup bot](https://eodly.io/use-cases/discord-standup-bot): How Eodly runs a daily standup in Discord with /checkin, reminds whoever is quiet, and sends one evening report checked against GitHub and Linear. Free for up to 5 people. - [Telegram check-in bot](https://eodly.io/use-cases/telegram-standup-bot): A daily check-in in Telegram from one t.me link: each person taps Start, answers in a private chat, and the lead gets one evening report. Free for up to 5 people. - [Slack standup bot](https://eodly.io/use-cases/slack-standup-bot): One Slack DM a day per person, one reminder, one evening report checked against GitHub and Linear. - [Best standup bots for Discord (2026)](https://eodly.io/blog/best-discord-standup-bots): Discord standup bots compared on price, free tier and features, checked on each vendor's site on 18 October 2026. - [Best daily check-in bots for Telegram (2026)](https://eodly.io/blog/best-telegram-standup-bots): Telegram standup and check-in bots compared on price, free tier and setup, checked 18 October 2026. - [Best Slack standup bots (2026)](https://eodly.io/blog/best-slack-standup-bots): Geekbot, DailyBot, Standuply, Range, Troopr, Standup and Prosper, Steady and more compared on price, free tier and integrations, checked 18 October 2026. - [Best tools to replace daily standups for a small remote team (2026)](https://eodly.io/blog/best-async-standup-tools): Async standup tools compared on what a 6-person team pays, free tier, chat tools and a one-line verdict, checked 18 October 2026. - [Tools that check status updates against GitHub commits (2026)](https://eodly.io/blog/check-status-updates-against-github-commits): Ten tools compared on how they connect written updates to commits and pull requests, with price and free tier, checked 18 October 2026. - [Geekbot alternatives (2026)](https://eodly.io/blog/geekbot-alternatives): Eight Geekbot alternatives compared on price, free tier, platforms and integrations, checked on each vendor's site 18 October 2026. - [When the Jira board says done](https://eodly.io/blog/when-the-jira-board-says-done): Five checks managers can add when Jira tickets keep bouncing back, and where a daily report fits next to Jira. ## About - [Eodly home](https://eodly.io): What Eodly is and who it is for. - [Privacy](https://eodly.io/privacy): How Eodly handles data. Eodly synthesizes work activity; it is not surveillance. - [Data processing addendum](https://eodly.io/dpa): Data processing terms.