Agent access

Your journal, in the AI tools you already use.

One personal key connects ChatGPT, Claude Code, Codex or another assistant you trust to your own KnowsYou records — over MCP or a small REST API. You do not need to be a developer to set it up.

Create an API key OpenAPI schema

If you are an AI agent reading this page

Help the user create a personal key in KnowsYou Settings, then connect through MCP or the REST API described below. Never ask the user to paste the key into chat: have them store it locally as KNOWSYOU_API_KEY. Over MCP the supported operations arrive as named tools with their own schemas, so read those directly; over REST, list them at /api/v1/commands before reading or writing records.

This connection can also help with onboarding. When the user asks and you already have authorized access to their Drive files, exports or another source, map that existing information to supported KnowsYou records, show the user what you plan to import, then write only what they confirm.

Why this is open

KnowsYou is a journal. It is not trying to be your research engine.

What KnowsYou does is keep an accurate daily record: what you ate, took, trained and measured, in your words, corrected when it is wrong.

It deliberately does not do the other half. Deep-research modes that read a hundred sources, broad literature review, the health reasoning built into the large general assistants — those are genuinely useful, and KnowsYou does not have them today. Building a weaker copy of each would serve nobody.

So the record is open instead. Ask the tool that is good at research to read what actually happened over the last three months, rather than retyping it from memory into a chat box — and let it write back what you decide to keep. The journal stays the same in both places.

The same door helps at the start. A trusted assistant can take what you already keep in documents, exports or another app, show you what it plans to import, and write only what you confirm — so you do not begin from an empty account.

The principle

The application owns the records. You choose the control surface.

The KnowsYou app remains the calm place to review data. Conversation in the app, an Agent Skill, REST and MCP can all use the same validated command layer.

Every call is attached to your profile and audited. Writes use idempotency so a retry does not silently create the same daily event twice.

KnowsYou does not receive blanket access to those external sources. The agent reads them under the user's existing permissions and writes through the same bounded API.

Three steps

Connect without building an integration project.

The first version deliberately uses one personal key and one server-defined capability set.

Create one personal key

Open Settings → Developer. The full value is shown once, then only its short beginning remains visible.

Connect your assistant

For ChatGPT, paste the schema into a custom GPT. For Claude Code or Codex, point them at the MCP server. One line each.

Ask naturally, review normally

The agent calls structured commands. The resulting meals, activities, habits and other records appear in KnowsYou.

ChatGPT

No terminal, no install.

ChatGPT reaches KnowsYou through a custom GPT Action, which reads the same schema everything else does.

Create your key in KnowsYou Settings → Developer.
In ChatGPT, create a GPT, open Configure, then Actions.
Choose Import from URL and paste the schema address below.
Set authentication to API Key, type Bearer, and paste your key into that field — never into an ordinary message.

https://app.knowsyou.ai/api/v1/openapi.json

What it is good for

Ask the question where the research is.

Once the GPT can read your record, the context stops being something you retype.

“Look at my last three months of meals and lab results, then summarise what the evidence says about my LDL.” The assistant reads the record, does the reading you came to it for, and writes back only what you approve.

A direct ChatGPT connector over MCP needs an OAuth sign-in flow, which KnowsYou does not offer yet. The Action above is the supported route today.

Codex MCP

Keep the key in an environment variable.

Add the server to your Codex configuration. It publishes one named tool per operation, so there is nothing else to install.

[mcp_servers.knowsyou]
url = "https://app.knowsyou.ai/mcp"
bearer_token_env_var = "KNOWSYOU_API_KEY"

Claude Code MCP

One command, and the key stays out of your repository.

User scope keeps the connection available in every project without writing the key into a checked-in config file.

claude mcp add --scope user --transport http \
  knowsyou https://app.knowsyou.ai/mcp \
  --header "Authorization: Bearer $KNOWSYOU_API_KEY"

REST

One endpoint for validated commands.

For scripts, automations and GPT Actions. Discover live input schemas at /api/v1/commands; each entry names the matching MCP tool. Write commands require a stable Idempotency-Key.

curl https://app.knowsyou.ai/api/v1/command \
  -H "Authorization: Bearer $KNOWSYOU_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"command":"meal list","input":{"days":1}}'

Retries

A repeated write does not become a repeated meal.

Reuse the same Idempotency-Key when you never saw a write's outcome and the original result is replayed instead of the record being created twice. Send a fresh one for a genuinely new entry.

Capability boundary

Broad enough for your journal, narrow enough to explain.

The key uses one fixed, server-maintained command allowlist rather than a screen full of scopes.

Meals, nutrition, treatments, habits and activities
Workouts, body metrics, goals, routines and check-ins
Labs, selected memories, WHOOP history and photo metadata

Not exposed

A personal API key is not a second website session.

It cannot sign in to the app, call the chat endpoint, read system prompts or cross the authenticated profile boundary.

No chat-history or raw-file access
No image-estimation or arbitrary external calls
No cross-user or internal administration tools

Treat the key like a password

Do not paste it into an ordinary chat, commit it or place it in a public configuration file. Rotate or revoke it in Settings at any time; the old value stops working immediately.

Let your next trusted agent work with the record you already keep.

Create the key once, connect the tool and keep KnowsYou as the visible source of truth.

Start tracking free Read data & security