OneMoreDay

Developers: API & MCP overview

OneMoreDay is built to be machine-readable. The mobile app is the source of truth for your data; this website and API let you — and the AI agents you trust — read your own OneMoreDay data programmatically.

Status: The public per-user API keys and hosted MCP server are rolling out in phases. This page documents the model and what's available today. Forward-looking items are marked (planned).

Principles

  • You only ever access your own data. Every credential is scoped to a single user. The API never exposes another user's data, and never exposes platform trade secrets (for example, the proprietary recipe and coaching content libraries).
  • Read-mostly. The app writes your data; the API is designed for reading your progress. Any write capability is tightly scoped and opt-in.
  • Least privilege. Keys are scoped to specific resources and are revocable at any time.

What you can read

The API is organized around the resources that make up your OneMoreDay life:

  • Profile & avatar — display name, level, HP (current/max) and state, total days alive, deaths.
  • Goals — your goals, schedules, and completions.
  • Progress events — XP, coins, streaks, and bonus events.
  • Workouts — sessions, plans, and progression.
  • Territory — your captured zones and leaderboard rank.
  • Badges — earned and available achievements.
  • Challenges & squads — your challenges, invites, and group activity.
  • Integrations — connection status for Strava, WHOOP, and Apple Health (status only — never raw tokens).
  • Summaries — weekly summaries of your progress.

The machine-readable contract for these endpoints lives in the OpenAPI specification.

Authentication

  • Today: the API authenticates with a Supabase session token (Authorization: Bearer <jwt>) issued when you sign in. Requests are scoped to the authenticated user.
  • Planned: personal API keys. From the website dashboard you'll be able to issue per-user API keys — hashed at rest, scoped to read-only resources by default, and revocable — so you can connect agents and tools without sharing your login. Keys never carry more access than you grant.

Connecting an AI agent (MCP) (planned)

OneMoreDay will host a Model Context Protocol (MCP) server so assistants like Claude and ChatGPT can connect directly to your data using your personal key. Once live, you'll add the OneMoreDay MCP endpoint to your agent, authorize with your key, and the agent can answer questions like "How's my streak?", "What goals did I miss this week?", or "How much territory have I captured?" — reading only your own data.

Discovery for agents

  • /llms.txt — a concise, linked index of this site for LLMs.
  • /llms-full.txt — the full knowledge base as a single text file.
  • /openapi.json — the OpenAPI 3.1 contract.
  • /.well-known/ discovery documents (planned) — for automated agent/tool onboarding.

Base URL

https://onemoreday-api.onrender.com

See the API reference for endpoints, request/response shapes, and examples.

Browse the API reference →