For AI agents
MyContext keeps what you've read in a shape a model can use: clean text, summaries, tags, highlights and a semantic index. An MCP server is on the way so agents like ChatGPT, Claude and Codex can plug straight in — and the REST API below already does everything it will, for anything that speaks plain HTTPS.
'%3e%3crect%20x='38'%20y='38'%20width='180'%20height='180'%20rx='54'%20fill='url(%23sb-body)'/%3e%3cg%20clip-path='url(%23sb-clip)'%3e%3crect%20x='38'%20y='38'%20width='180'%20height='180'%20fill='url(%23sb-glow)'/%3e%3crect%20x='38'%20y='38'%20width='180'%20height='180'%20fill='url(%23sb-depth)'/%3e%3crect%20x='46'%20y='42'%20width='164'%20height='78'%20rx='40'%20fill='url(%23sb-sheen)'/%3e%3c/g%3e%3crect%20x='38.75'%20y='38.75'%20width='178.5'%20height='178.5'%20rx='53.25'%20fill='none'%20stroke='%23ffffff'%20stroke-opacity='0.35'%20stroke-width='1.5'/%3e%3crect%20x='86'%20y='102'%20width='26'%20height='54'%20rx='13'%20fill='%230c121b'/%3e%3crect%20x='144'%20y='102'%20width='26'%20height='54'%20rx='13'%20fill='%230c121b'/%3e%3ccircle%20cx='94.5'%20cy='113'%20r='4.5'%20fill='%23ffffff'%20fill-opacity='0.9'/%3e%3ccircle%20cx='152.5'%20cy='113'%20r='4.5'%20fill='%23ffffff'%20fill-opacity='0.9'/%3e%3c/g%3e%3c/svg%3e){kind=small}
# search the vault by meaning
curl "https://mycontext.work/api/public/v1/bookmarks" \
--data-urlencode "q=pricing experiments after:2026-01-01" -G \
-H "Authorization: Bearer kp_…"
# → { "bookmarks": [ { "id": "…", "title": "…",
# "summary": "…", "tags": ["pricing", "experiments"],
# "url": "…" } ] }What an agent can do
The API is the same one the browser extension and the app's shortcuts use. There's no second-class “integration” surface — an agent gets Dex's full reading.
One call runs the same hybrid search you use in the app: full text, semantic similarity and the query language (#tag, is:unread, after:, url:, -not). Results come back with Dex's summary and tags, so an agent can decide what to open without reading everything.
Opening an entry returns the readable article text, the summary, the tags, your note, reading progress and every highlight with its note. No scraping, no boilerplate — the version Dex already prepared.
Agents can file links, notes and text with tags and a list. Ask for processing and Dex reads it synchronously so the summary and tags are in the response; leave it off and the app catches up in the background.
Agents can mark passages and attach notes (labelled as AI-written so you can tell), and call the same grounded “Explain this” you use in the reader.
Show, don't tell
curl -X POST https://mycontext.work/api/public/v1/bookmarks \
-H "Authorization: Bearer kp_…" \
-H "Content-Type: application/json" \
-d '{
"url": "https://example.com/pricing-memo.pdf",
"note": "Read this before Tuesday'\''s review",
"tags": ["pricing", "q4"],
"process": true
}'GET https://mycontext.work/api/public/v1/bookmarks/{id}
→ {
"bookmark": {
"title": "…", "url": "…", "summary": "…",
"tags": ["…"], "note": "…",
"text_content": "clean article text…",
"word_count": 1840, "read_progress": 0.35,
"highlights": [ { "text": "…", "note": "…" } ]
}
}// an agent writing down what it learned, as a note
await fetch("https://mycontext.work/api/public/v1/bookmarks", {
method: "POST",
headers: { Authorization: `Bearer ${KEY}`, "Content-Type": "application/json" },
body: JSON.stringify({
title: "Decision: keep the free plan at 1,000 entries",
text: "Agreed in the 25 Sep review. Reasons: …",
tags: ["decisions", "pricing"],
}),
});API reference
Base URL https://mycontext.work/api/public/v1. Authenticate every call with Authorization: Bearer kp_…. Requests and responses are JSON; CORS is open so browser-side tools work too.
| Method | Path | What it does |
|---|---|---|
| GET | /meWho this key belongs to: display name, email, entry count, lists and tags. | Who this key belongs to: display name, email, entry count, lists and tags. |
| GET | /bookmarks?q=…&limit=…Hybrid search with the query language. `?url=` looks up whether a page is already saved. | Hybrid search with the query language. `?url=` looks up whether a page is already saved. |
| POST | /bookmarksSave a `url` or `text`, with optional `title`, `note`, `tags`, `listId`, `process`. | Save a `url` or `text`, with optional `title`, `note`, `tags`, `listId`, `process`. |
| GET | /bookmarks/:idFull entry: clean text, summary, tags, note, reading data and highlights. | Full entry: clean text, summary, tags, note, reading data and highlights. |
| PATCH | /bookmarks/:id`title`, `note`, `favourited`, `archived`, `read`, `addTags`, `listId`, `process: "crawl" | "enrich" | "all"`. | `title`, `note`, `favourited`, `archived`, `read`, `addTags`, `listId`, `process: "crawl" | "enrich" | "all"`. |
| DELETE | /bookmarks/:idRemove an entry permanently. | Remove an entry permanently. |
| GET · POST | /bookmarks/:id/highlightsList or add highlights (`text`, `color`, `note`, `noteSource`). The same passage twice is one highlight. | List or add highlights (`text`, `color`, `note`, `noteSource`). The same passage twice is one highlight. |
| PATCH · DELETE | /highlights/:idRecolour, annotate or remove a highlight. | Recolour, annotate or remove a highlight. |
| POST | /explainStream a grounded explanation of `text` from `bookmarkId` (`mode`: explain, simplify, context). | Stream a grounded explanation of `text` from `bookmarkId` (`mode`: explain, simplify, context). |
| DELETE | /meRevoke the key this request was made with. | Revoke the key this request was made with. |
Signed-in users can also copy ready-made examples from Settings → API keys.
Patterns
Search → open → cite. The agent answers from what you actually read and links back to the entry, instead of guessing from the open web.
Anything that can call a URL can save: a Shortcut on your phone, a Slack bot, a cron job that files a weekly report. It lands in the same vault, read the same way.
Let an agent write notes about decisions, preferences and things it learned. They're searchable by meaning next session — by the agent and by you.
MyContext doesn't care which model calls it. Dex does the reading and indexing once; whatever you run on top just asks.
Trust
Access should be easy to grant and easier to take away.
Keys are created in Settings → API keys, scoped to your vault, and named so you know which agent holds which. Make one per agent.
Delete a key and every request with it fails immediately. The extension uses the very same mechanism, so there's one place to look.
Notes and titles written by an agent or by Dex carry an AI mark in the app, and never overwrite a title you typed yourself.
Questions
It's what we're building next. MCP is the native way for agents like ChatGPT, Claude and Codex to connect: your vault will appear as a set of tools they can search, read and write through, signed in as you. Until it ships, everything it will do is already possible through the REST API below — and the MCP server will be built on exactly these endpoints, so nothing you wire up today is wasted.
Yes. An entry is an entry regardless of who saved it — that keeps the plan honest and the API simple.
Today a key sees your whole vault, exactly as you do. Create a separate key per agent so you can revoke one without touching the others; finer-grained scopes are something we're considering.
No published hard limit today; the API is meant for personal automation, not crawling. Processing calls (process: true) are the slow path because Dex reads the page before replying — use them when you need the summary right away, and let the background catch up otherwise.
Dex uses commercial models through our own gateway; you don't need a key of your own and never see the provider. Your agents, on the other hand, can run on anything — they talk to MyContext, not to Dex's model.
One vault, read once, open to you and to whatever you build. Create a key in Settings and you're calling it in a minute.