Documentation

Welcome to the Mikipage documentation. Mikipage is the AI-powered wiki — write notes freely, and AI organizes them into shareable pages for you and your groups. Use the sections below to find what you need.

Getting Started

[1] — Getting Started with Mikipage

New here? Start with this guide. It walks through the three-step loop — write, organize, share — and explains the key ideas you need to make sense of everything else. Includes a table pointing to every other guide.

[2] — The Alpha

What alpha means in practice: features and workflows may change quickly, and bugs or rough edges remain likely. Explains free background AI sweeps, which run roughly every 6–12 hours by default for your Personal space and groups you own, use no credits, and can be turned off in Account → AI Settings. Background-sweep availability and frequency may change; use credits for an immediate AI run.

[3] — Notes, Pages, Groups, and Spaces

The four words that cover almost everything. Read this early to understand the distinction between a note (something you wrote, static, yours alone) and a page (something AI wrote from your notes, kept current). Also explains groups, spaces, and comments.

[4] — Moving from Notion to Mikipage

A practical guide for bringing knowledge from Notion while keeping Mikipage focused on write → AI organize → share. Learn what converts well to notes, which database and workflow features remain better suited to Notion, how to export and prepare Markdown and CSV content, check attachments and links, import in a small private pilot, and create AI-maintained pages from the imported material.

Core Features

[5] — Writing Notes

How to create, edit, protect, and format notes. Covers auto-save and draft recovery; Markdown and Plain editors; sharing, starring, archiving, hashtags, note references, attachments, and LaTex math. Explains browser-encrypted protected notes, why AI needs text descriptions for attached files, and the 32KB note limit.

[6] — Organizing Notes

Learn how to use Stack, Mikipage’s temporary collection for acting on several notes at once. Covers selecting and reviewing notes, batch starring, archiving, group sharing, pinning notes to an open page, eligibility rules, and inserting note references from Stack.

[7] — Markdown in Mikipage

The complete Markdown reference for notes — standard syntax (bold, italic, headings, lists, quotes, links, tables, fenced code) plus every Mikipage extension: first-line titles, hashtag tags, LaTeX math (inline and display), preformatted blocks, timelines, table of contents, note-to-note references, inline attachments, and navigation blocks (for sidebar menus). Includes toolbar shortcuts for every piece of syntax and notes on what travels to other Markdown tools.

[8] — Working with Pages

How to create an AI-maintained page, write effective instructions, and navigate its Page and source-note views. Covers All notes and Manual modes, pinning and removing notes, Stack-based batch pinning, incremental versus full refreshes, staleness markers, scheduled free background sweeps, layered instructions, Save as Note, and practical page limits.

[9] — Finding Your Notes: Quick Search vs Full Search

The search box has two modes: quick search (instant, keyword, covers your 100 most recent notes) and full search (press Enter — semantic, covers your entire history). Explains when to use each and how filters work.

AI & Automation

[10] — Running AI: Three Ways

Three ways to get AI to do work in Mikipage — on the website (uses AI credits), via a connected AI assistant through MCP (uses your own subscription), or via the API (your choice). Covers free background sweeps roughly every 6–12 hours by default, what on-demand operations cost, how AI credits work, and how to keep pages current automatically using ai_refresh.py on a schedule (cron or an AI assistant) at no Mikipage credit cost. Also covers the Translate feature for multilingual groups and the AI Polish note-editing tool.

[11] — Connecting an AI Assistant (MCP)

How to connect Claude, ChatGPT, Claude Code, or any MCP-compatible assistant using Mikipage’s OAuth connection URL. Explains setup, including ChatGPT personal-plugin installation, what assistants can do (refresh pages, write notes, search your corpus, and maintain page associations), deliberate restrictions such as no deletion or account changes, and why MCP-driven work costs no Mikipage AI credits.

[12] — Publish Your Content to the Public

How to make notes and pages publicly readable at a mikipage.com/public/… URL — no account required for readers. Covers creating a public group, setting a friendly alias, designating a home page, and adding a sidebar. Explains how sidebars work on public and private pages, and includes examples for a personal blog, a fan wiki, and this documentation site.

Security & Privacy

[13] — Security

A specific, non-reassuring look at how Mikipage protects your data technically. Covers where data lives (AWS us-east-1, encrypted in transit and at rest), who can read your notes, and protected notes — notes encrypted in your browser with a password that never leaves it, making them unreadable to Mikipage itself. Explains how to protect a note, the locked/unlocked states, the visible description, attachment limitations, password recovery (there is none), and the AES-256-GCM + PBKDF2 scheme under the hood. See also the companion [14] for the team's commitments and promises.

[14] — Security and Privacy Pledge

The promises Mikipage makes about how it handles your data — not just the technical controls, but the team's commitments. Covers the two-person rule (no one opens production data alone), a firm commitment never to sell or rent your data, and what happens when you want to leave (full deletion within 30 days). Read this alongside the Security guide for both the "how" and the "who."

Legal

[15] — Terms of Service

The full legal agreement between you and Knowsun LLC for using Mikipage. Covers account responsibilities, your ownership of your content and the limited licence you grant Mikipage to operate the service, AI-generated content caveats, acceptable use, plans and payment (including AI credits, renewals, and refunds), suspension and termination, disclaimers and liability limits, and governing law (Michigan). Plain-language summaries precede the formal sections. Read alongside the [14] for the team's data-handling commitments.

For Developers

[16] — Mikipage API

The complete REST API — every feature the product offers, with no options hidden. Covers the Python SDK, base URL and conventions, OAuth 2.1 authentication, scope model, and a full endpoint reference for notes, pages, attachments, groups, comments, publishing, AI runs, chat, account, and public access. Includes a quickstart and a list of features in progress.

Reference

[17] — Limits

Every enforced ceiling in one place. Covers plan-based note and page quotas (100/20 on Free up to 20,000/500 on Pro), note size (32KB text, 10MB/10 files per attachment), page limits (notes matched and read per refresh, output length, pages per space), group size (30 members), and version history (last 5 versions for 30 days). Includes practical advice for what to do when you approach each limit — splitting pages, narrowing instructions, or attaching files instead of pasting long content.

[18] — Frequently Asked Questions

Short answers to the most common questions — getting started and support, notes, pages, groups, privacy (including protected notes, the Security guide, and the Security and Privacy Pledge), integrations, and what the alpha stage means for you. Covers free background sweeps roughly every 6–12 hours by default, with availability and frequency subject to change. Each section links to the relevant detailed guide.

[19] — Pricing

Covers the three plans — Free, Starter, and Pro — including note, page, public-group, export, and weekly AI-credit allowances. Starter is paid through Stripe: choose a price from $5 every six months; Pro is by arrangement. Explains purchasing 5,000 AI credits for $5.99, the 500 free introductory credits and their 30-day expiry, free background sweeps roughly every 6–12 hours by default, and why MCP or client-execution API usage costs nothing. Also covers feature-complete paid tiers, cancellation, exportability, and the Longevity Pledge.

[20] — Longevity Pledge

Mikipage's standing commitment to long-term continuity. Explains why the product isn't at risk of a forced sale (no venture capital), how its serverless architecture keeps costs proportional to usage, and what happens to your data if Mikipage ever shuts down: at least 90 days' notice, export working until the last day. Also covers the four ways to hold a copy of your notes independently — one-button export, plain Markdown storage, the full API, and the Obsidian plugin — so your notes never depend on Mikipage continuing to exist. For the team's data-handling promises (including deletion on request), see [14].

Have a question not answered here? Use Ask in the top bar (or the Ask tab on a phone), browse Help in the space switcher, or email support@mikipage.com.