Running AI: Three Ways
Everything AI does in Mikipage — finding which notes belong to a page, writing the page, suggesting new pages, answering questions — needs a language model. There are three ways to get one, and the difference between them is simply who pays for the model call.
| Who runs the model | What it costs you | |
|---|---|---|
| On the website | Mikipage | AI credits |
| Via MCP | Your AI assistant | Nothing — your existing subscription |
| Via the API | Your choice | Credits, or nothing if you run it yourself |
If you already pay for Claude or a similar assistant, MCP is the best deal available: see [1].
1. On the website
The simplest path. You click a button, Mikipage runs the AI on its own infrastructure, and your AI credits pay for it.
What you can trigger
| Operation | Where | Credits |
|---|---|---|
| Refresh All — update every page in the space | Organize | Yes (needs 50+) |
| Refresh — update one page | the page itself | Yes |
| Suggest pages — AI proposes pages from your recent notes | Organize | Yes |
| Add to related Pages (Automatic) — match a note against the space's pages | a note | Yes |
| AI Polish — AI-assisted edit of a note | markdown editor toolbar | Yes |
| Chat — ask questions about your notes | the chat button, any page | Yes |
| Accepting a suggestion, attaching a page by hand, pinning a note | — | No |
Two things on that list deserve a note of their own.
AI Polish is the only AI operation that touches a note, and it's deliberately timid: it appends its version to the bottom of your note rather than replacing what you wrote. You can pass instructions and choose a model. Nothing else in Mikipage ever modifies a note.
Chat is grounded in your own notes and your groups' notes — it reads your corpus with tools rather than searching the web. Opened from a note or a page, it knows about that page and can answer questions on it.
How AI runs behave
All of it is fire-and-forget. You trigger a run, get a toast saying it started, and carry on working; a notification arrives when it's done and the affected page updates itself. You never wait on a spinner.
AI credits
- New accounts start with 500 free credits.
- Below 10 credits, AI buttons switch off with "Low credit, cannot run AI". Refresh All needs 50, since it's a batch.
- Your balance shows next to every AI button, and in full — with a transaction-by-transaction ledger — under Account → Usage.
- Credits are consumed in proportion to the work actually done. Content that hasn't meaningfully changed since it was last processed isn't reprocessed, so refreshing a page that's barely moved costs very little.
See [2] for where pricing is headed.
2. Via MCP — use your own AI subscription
This is the recommended path for anyone who already pays for an AI assistant.
MCP (Model Context Protocol) connects Mikipage to an assistant like Claude as a tool it can use. When you ask your assistant to refresh your pages, your assistant does the reading and the writing, using the subscription you already have, and hands the results back to Mikipage.
No Mikipage credits are consumed — and not as a billing courtesy. No MCP tool can trigger a server-side AI run at all; there is nothing for Mikipage to charge for. The thinking happens entirely on your assistant's side.
In practice this works well for:
- "Refresh all my pages" — the assistant asks Mikipage what's out of date, works through it, and writes each page back.
- "Update this page" — read the page and its notes, synthesize a fresh version.
- Capturing from a conversation — "save that to Mikipage" mid-chat.
Setup takes about a minute: [1].
3. Via the API — either way, your choice
The REST API is the complete feature set, and it exposes the choice directly. An AI run is
created with POST /api/runs, and one field decides who does the work:
execution: "server"queues the job on Mikipage's infrastructure. Billed to your credits.execution: "client"returns anllm_inputpayload instead of running anything. You send that to whichever model you like — Claude, OpenAI, something local — and post the result back. No credits are charged, because Mikipage never called a model.
That second mode is how MCP-style clients work, and it's available to your own scripts too. Run types cover the whole surface: page refresh, analyze, generate, note-to-page matching, page-to-note matching, note editing, page suggestion, and space-wide refresh-all.
Full details, endpoints, and the Python SDK: [3].
A note on the alpha
AI updates are user-triggered. There is no server-side sweeper refreshing your pages on a schedule — if a page is out of date, it stays that way until you (or your AI assistant) ask for a refresh. A scheduled sweeper is planned; credits will apply to it when it arrives.