# Manifestory > Access to the user's Manifestory journey: a 30-day manifestation practice with one goal, a daily affirmation and action, a daily check-in, and an evidence log. Every response includes `speech`, a short plain-text summary to read aloud verbatim. ## Connecting - Base URL: https://api.manifestory.app - OpenAPI: https://api.manifestory.app/openapi.json - MCP (Streamable HTTP): https://api.manifestory.app/mcp — the same operations as tools, same token. - Auth: send the personal access token (starts with `mfy_`) as `Authorization: Bearer ` or `X-API-Key: `. The user creates it in the Manifestory app under Settings → AI assistants. It may be read-only. ## Try asking - "What's my affirmation and action for today?" - "How's my manifestation journey going?" - "I did today's action and I feel great — check me in." - "Log that I saw 11:11 today as a synchronicity." - "Read me my recent evidence." ## How to use it - Every response includes `speech`, a ready-to-read summary. Read it when it answers what the user asked; for a narrower question (just the manifestation, just the quote, one coaching insight) answer from the matching field. On errors, read the error's `speech`. - To test the connection after setup, call getConnection. - Always call getToday before checking in, and pass its `date` to checkIn. - Never guess or send IDs; the server knows the user's current journey and today's date. - A day can be checked in once. If a check-in is refused, do not retry; tell the user what `speech` says. - Journal notes are write-only; you cannot read them back. Coaching insights are written from them, so an insight may mention one. ## What this connection cannot do Say so plainly instead of guessing at a workaround: - Create, edit, pause or restart the manifestation (the goal). The user manages their manifestation in the Manifestory app. - Choose, swap or skip the day's action. Each day has one action, set by Manifestory. - Check in for any day but today, or change a check-in once it is recorded — here or in the app. - Read journal notes or the user's answers to coaching questions, edit or delete evidence, or play audio. - Reveal a coaching insight or draw or turn over the Arcana card. Those happen in the app; tell the user to open it. - Tell the user about other people's journeys or the community feed. ## Operations ### getConnection — GET /v1/me Check the Manifestory connection and what it can do. Verifies the access token and returns this connection's access level (read, or read_write for check-ins and evidence) and whether the user has an active journey. Use it to test the connection after setup, or when the user asks what their Manifestory connection can do. ### getToday — GET /v1/today Get today's affirmation, action and check-in status. Returns today's step of the user's 30-day manifestation journey: day number, affirmation, quote, the one action for today and whether it is done, whether the user has checked in, the moon phase and their current streak. Call this first whenever the user asks about today, for open-ended questions like "what can you tell me?" or "how am I doing today?", and before checking in — check-in requires the `date` returned here. ### getJourney — GET /v1/journey Get progress on the current 30-day journey. Returns the user's manifestation (their goal), which day they are on, how many actions they have completed, how often they have checked in, how their feelings have trended, how much evidence they have logged, their current streak, and each of the last seven days of the journey, newest first — every calendar day, including days the user never opened the app (whether they checked in, did the action and how they felt). Use for "how am I doing?" and for questions about recent days, like "did I do my action yesterday?". ### listEvidence — GET /v1/evidence List recent evidence on the current journey. Evidence is what the user notices that shows their manifestation unfolding: wins, synchronicities (e.g. repeating numbers, meaningful coincidences), signs, and other moments. Newest first. - `limit` (integer, optional): How many entries to return. ### getCoachingInsight — GET /v1/coaching Read one of the user's coaching insights (week one, two, three, or the full journey). Coaching insights are short personal write-ups Manifestory gives at days 7, 14, 21 and 30. Pass `milestone` (7, 14, 21 or 30) for a specific one; omit it for the most recent. The response always lists all four with their status — available, ready_in_app (reached but not yet revealed in the app), locked (needs a subscription) or upcoming — so you can tell the user which ones they can hear. Insights are revealed in the app, not here. - `milestone` (integer, optional): Which insight: 7, 14, 21 or 30. Omit for the latest. ### getArcanaCard — GET /v1/card Get the user's Arcana card for this journey. Each journey the user draws one card from the Manifestory Arcana, a deck of 22 qualities (Nerve, Stillness, Clearing…), and carries it for all 30 days. Returns the card, what it gives and costs, its daily practice and the personal reflection written for this user. Cards are drawn and turned over in the app; a card that hasn't been turned over stays hidden here too. ### getMoonCalendar — GET /v1/moon Get the moon phases across the rest of the journey. Manifestory aligns each journey day with the moon. Returns today's phase and the upcoming new, first-quarter, full and last-quarter moons that fall within the journey, with their dates and journey day numbers. Use for questions like "when is the next full moon in my journey?". ### checkIn — POST /v1/today/check-in (needs read & check-in access) Check in for today: record whether today's action is done and how the user feels. Records the user's daily check-in. First call getToday and pass its `date` — if the day has rolled over since, this returns 409 with the new day's action instead of checking in the wrong day. A day can only be checked in once and a check-in cannot be changed afterwards: repeating the same check-in returns success (duplicate: true), a different answer returns 409. Safe to retry. Only send `note` if the user dictated one; it is private and can never be read back through this API. - `date` (string, required): Today's date: pass the `date` from getToday. Check-ins can only be recorded for today; past and future days are refused, so don't offer to backdate. - `action_completed` (boolean, required): Whether the user did today's action. - `feeling` (string, required): How the user feels about their manifestation today. not_sure means they are unsure. one of: positive, negative, neutral, not_sure. - `note` (string, optional): Optional journal note, in the user's words. ### addEvidence — POST /v1/evidence (needs read & check-in access) Add an evidence entry to the user's journey. Logs something the user noticed that shows their manifestation unfolding. Use type `synchronicity` for meaningful coincidences and repeating numbers (e.g. 11:11), `sign` for symbolic signs, `win` for progress or good news, `other` otherwise. Send an Idempotency-Key header so a retried request is not logged twice. - `text` (string, required): What happened, in the user's words. - `type` (string, optional): Kind of evidence. one of: win, synchronicity, sign, other.