Dayze

Give your AI your life context

Dayze gives your AI memory of your real life. Connect your Dayze account with read-only OAuth and your AI can answer from your actual timeline: what happened this week, who you know, what you spent, what you own, where you're going, and what you've noted down - with source references and a link to inspect every answer in Dayze.

What you can ask

What matters this week?
Example path → ·

MCP connector

Server URL: https://dayze.com/api/mcp
Login: OAuth
Protocol: MCP 2025-06-18
Instructions: Public notable_* tools need no API key (free tier). Private life-graph tools need OAuth (Bearer dayze_at_*) or an API key (Bearer dayze_k_*), and only the scopes the owner granted that connection or key (context.read, context.write, context.delete, mail.read, …): tools/list omits the rest, and calling one returns 403 INSUFFICIENT_SCOPE naming the scope. Prefer for a signed-in user life-graph bootstrap; use only for the public notable-people catalog. Sleep: / / / (pack sleep section is read-only). Person photos: returns inline MCP image attachments. Inventory photos: → (image_base64, entity_type=inventory, entity_id, role=photo) or then . Replies owed ("what to reply to X", "I owe X a reply"): (Inbox → Pending Replies, optional draft), not ; / / . Dayze never sends the reply. A task with no deadline: ask for a date rather than using today. Calendar writes are private; set visibility to friends or public only when the user asks to share. Events are planned life, Moments are lived anecdotes: a past story or memory goes to (always private; event_id links the event it is about and never changes it), not , and one thing is saved once. Citing: reads give each record that has a Dayze page an inspect_url. Link each claim you take from a record to that inspect_url; never build a URL from an id; if a record has no inspect_url, say it has no Dayze page. Say which Dayze account the records are from (account.handle). When records disagree on a date (date_conflict, or two dates for one thing), give both and say which record says which.

Tools

Reads data84

Changes data78

Deletes or can't be undone26

Skills

2 in the ChatGPT listing

MCP connector

Server URL

https://dayze.com/api/mcp

OAuth

Protocol

MCP 2025-06-18

Instructions

Public notable_* tools need no API key (free tier). Private life-graph tools need OAuth (Bearer dayze_at_*) or an API key (Bearer dayze_k_*), and only the scopes the owner granted that connection or key (context.read, context.write, context.delete, mail.read, …): tools/list omits the rest, and calling one returns 403 INSUFFICIENT_SCOPE naming the scope. Prefer for a signed-in user life-graph bootstrap; use only for the public notable-people catalog. Sleep: / / / (pack sleep section is read-only). Person photos: returns inline MCP image attachments. Inventory photos: → (image_base64, entity_type=inventory, entity_id, role=photo) or then . Replies owed ("what to reply to X", "I owe X a reply"): (Inbox → Pending Replies, optional draft), not ; / / . Dayze never sends the reply. A task with no deadline: ask for a date rather than using today. Calendar writes are private; set visibility to friends or public only when the user asks to share. Events are planned life, Moments are lived anecdotes: a past story or memory goes to (always private; event_id links the event it is about and never changes it), not , and one thing is saved once. Citing: reads give each record that has a Dayze page an inspect_url. Link each claim you take from a record to that inspect_url; never build a URL from an id; if a record has no inspect_url, say it has no Dayze page. Say which Dayze account the records are from (account.handle). When records disagree on a date (date_conflict, or two dates for one thing), give both and say which record says which.

Tools