Skip to main content
DayzeHelp
Back to Dayze

Dayze API

Dayze · founded by Luke Goh

Build on top of Dayze. Access user data, events, people, and insights programmatically.

Connect Dayze MCP →

Connect your Dayze account

Sign in to Dayze, then open Settings → Agent access to create an API key or manage connected OAuth apps.

What You Can Build

Life Dashboard Widgets

Embed Dayze data in your own apps — Day Score, events, streaks.

Data Import / Export

Migrate data in and out of Dayze programmatically.

Custom Integrations

Connect services we don't natively support yet.

Analytics & Research

Build research tools on aggregated, anonymized data.

API plans

Developer Beta is free during private beta. Signed webhooks are available on API Pro and Enterprise. Plan details are also available on Pricing.

Developer Beta

Freeduring private beta

600 requests / hour

  • · REST v1 + MCP (life context, events, people)
  • · Scoped API keys
  • · Community support

Pro API

$49/ month · USD

10,000 requests / hour

  • · Everything in Developer Beta
  • · Webhooks (coming soon)
  • · Higher rate limits

Enterprise API

Customannual contracts

Custom limits + SLA

  • · Dedicated infrastructure options
  • · OAuth for your users
  • · Module / partner program

API endpoints

GET/api/openapi
GET/api/v1/context
GET/api/v1/webhooks
POST/api/v1/webhooks
PATCH/api/v1/webhooks
DELETE/api/v1/webhooks
GET/api/v1/mcp
POST/api/v1/mcp
GET/api/v1/events
GET/api/v1/people

For the supported connection methods and tool examples, see Agents & MCP.

Authentication

The Dayze API uses Bearer token authentication. Create an API key in Settings → Agent access. Third-party apps use OAuth 2.1 authorization code + PKCE with the https://dayze.com/api/v1 resource and explicit scopes. See the OpenAPI 3.1 reference or the client-specific instructions in Agents & MCP.

curl -X POST https://dayze.com/api/v1/mcp \
     -H "Authorization: Bearer YOUR_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{"tool":"get_context_pack","parameters":{}}'

Scopes and rate limits

A Read only key (context.read) can call GET /api/v1/context, /events, /people and the MCP read tools. Pulse, activity, net worth and actions each need their own scope, which you can add to a Custom key. Webhooks need webhooks.read or webhooks.write and the Pro API plan. The OpenAPI reference lists the scopes each endpoint accepts.

Each key has its own limit, shown under Settings → Agent access → API keys: 10 requests a minute on Developer Beta and 167 on Pro API, counted per clock hour (600 and about 10,000). Over it, you get 429 with Retry-After. Responses from /context, /events and /people report the key's limits as X-RateLimit-Limit (per minute) and X-RateLimit-Limit-Day. Every /api/v1 request also counts toward a per-IP ceiling of 100 a day; responses to requests without a key report that one as X-RateLimit-Limit: 100.

Quick Start

# Get your life context
curl -X POST https://dayze.com/api/v1/mcp \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"tool": "get_context_pack"}'
# Search your memories
curl -X POST https://dayze.com/api/v1/mcp \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"tool": "search", "parameters": {"query": "birthday celebrations"}}'

MCP Endpoint Reference

The POST /api/v1/mcp endpoint exposes Dayze as a Model Context Protocol tool server. External AI agents can read your life data and write structured life (CRM, food, calendar events) through these tools. Request body: { "tool": "...", "parameters": { ... } }.

get_context_packCompact life context pack; use parameters.query to focus the request
get_life_graphLife graph — people (nodes), person_connections (edges), optional event↔people links (parameters: include_event_links, event_links_limit, max_people)
get_person_neighborhoodOne person plus every person_connection they participate in (parameter: person_id)
get_eventsCalendar events (parameter: range = today | week | month | year | decade)
get_peopleFlat list of contacts (no edges — use get_life_graph for relationships)
update_personCRM write — patch one owned person_id (is_favorite, tier, relationship, notes replace, birthday). Rebuilds life_state. Share tokens denied
log_foodFood Diary write — what + meal_period/consumed_at + optional with (Mum/Dad/my parents). Mirrors to calendar. Example: Mee Pok late lunch with parents
update_foodFood Diary patch — owned food_id + optional log_food fields. Example: add hot tea onto Salmon Bento. Unknown / other-user id errors; does not insert. Share tokens denied
log_eventCalendar write — title + date + optional time/location/category/with. Example: funeral tonight for Mr Goh Choo Taw, 8pm, then Sunday cremation at Mandai
update_eventCalendar patch — owned event_id + optional log_event fields. Unknown / other-user id errors; does not insert. Share tokens denied
log_favorite_songMusic favorites write — title + artist, or track as "Artist - Title (year remaster)". Example: Henry Mancini - Piano And Strings (1995 Remastered). Share tokens denied
get_memoriesRecent Dayze Agent memories; query also returns matching events/people (prefer search for trips)
get_expensesCashflow summary: spend, income, net (parameter: period = month | year)
get_trackersLive trackers / streaks (no expired countdowns)
searchPhrase-first life search (parameter: query, optional limit); excludes Browsed titles

Get API access

Sign in, open Settings → Agent access → API keys, and choose Create API key. Select the access your integration needs, then choose Generate key.

Open Agent access
Privacy & DataAgents & MCP →