Gentic Wiki — Documentation

1. Getting Started

Sign Up & Get Your API Key

Before you can use Gentic Wiki, you need an API key to authenticate your requests.

1. Go to gentic.co/wiki and create an account.
2. Create an organization from your dashboard. API keys and billing are scoped to the organization.
3. Generate an API key and use it as a Bearer token in your MCP client.

2. Connecting to the MCP Server

The server is available at https://mcp.gentic.co/wiki. For Claude Code:

claude mcp add gentic-wiki \
  --transport http \
  https://mcp.gentic.co/wiki \
  --header "Authorization: Bearer YOUR_API_KEY"

For Claude Web and ChatGPT you can also connect via OAuth — no API key needed. See the connect section on the landing page for other MCP clients (n8n, OpenClaw).

3. Agent Skill

For the best results, pair the MCP server with the Gentic Wiki agent skill. The MCP server gives your agent tool access; the skill teaches it the optimal workflow order. Both the raw SKILL.md and a ready-to-upload .skill bundle are generated on demand from the live manifest, so they always reflect the current tools and pricing.

Add the skill directly via URL:

https://gentic.co/wiki/SKILL.md

Or upload a .skill bundle to Claude Managed Agents:

https://gentic.co/wiki/gentic-wiki.skill

Download this file and upload it wherever Claude Managed Agents asks for a .skill file. It's a zip bundle generated on demand from the latest SKILL.md.

4. When to Apply

• User wants to turn research notes, briefs, or reports into a structured wiki.
• User wants to query their org's accumulated knowledge in natural language and get cited answers.
• User mentions "wiki", "entity pages", "backlinks", "wikilinks", or wants to roll up findings across ideas.
• User wants to view a wiki page with backlinks, or check the wiki for broken links and orphan pages.
• User has a new artifact (e.g. a research note from `startup_save_research_note`) and wants to fold it into the wiki.

5. Workflow

1. 1. Pick a scope: idea vs org

   Two scopes. **Idea scope** (`{ kind: 'idea', ideaSlug }`) ingests a source attached to a specific idea — the source's S3 key must live under that idea's prefix. **Org scope** (`{ kind: 'org' }`) ingests org-shared artifacts, _or_ rolls up across all idea wikis when paired with `{ from_ideas: true }`. Pick idea scope by default when working inside an idea; reach for org scope only for org-shared sources or roll-ups.

2. 2. Ingest sources, not arbitrary text

   `wiki_ingest` takes an `s3_key` pointing at a raw-source artifact already inside the calling org (e.g. `orgs/{org}/ideas/{slug}/research-notes/foo.md`). The key cannot point at an existing wiki-layer page — the wiki ingests _into_ itself, it doesn't ingest itself. If the user wants to add a new note, save it as a raw artifact first (e.g. via `startup_save_research_note`), then point `wiki_ingest` at the resulting S3 key.

3. 3. Serialize concurrent ingests on the same scope

   Concurrent ingests on the same scope race on the snapshot read and last-write-wins on overlapping entities. If you're ingesting a batch, **run them sequentially per scope** — don't fan out parallel `wiki_ingest` calls into the same idea or the same org. Different scopes are independent and safe to parallelize.

4. 4. Query with the right scope

   `wiki_query` defaults to `scope: 'all'` — searches both org-level and idea-level pages. Narrow with `scope: 'org'` for org-shared knowledge only, or `scope: 'idea'` + `ideaSlug` to search inside a single idea's wiki. Always surface the cited wiki paths back to the user so they can open the source pages — that's the whole point of an agent-native wiki.

5. 5. View pages with backlinks

   `wiki_view` renders a page with `[[wikilinks]]` rewritten as clickable references and a 'Referenced by' section appended (toggle off with `includeBacklinks: false`). Use the `path` argument with values like `'index'`, `'log'`, `'entities/core-customer'`, or `'ideas/irestore/entities/customer'`. Omit `path` to view the org homepage. Pages live under `orgs/{org}/wiki/...` — see WIKI.md for the schema.

6. 6. Lint after batches and on a schedule

   `wiki_lint` is read-only and free. It surfaces broken wikilinks, orphan entity pages (no inbound links), missing index entries, and stale index entries (pointing at deleted pages). Run it after a batch of `wiki_ingest` calls, or schedule it periodically. Default `scope: 'all'`; narrow to `'org'` or `'idea'` (with `ideaSlug`) to limit the pass.

7. 7. Roll up across ideas

   When the user wants org-wide insights from per-idea wikis (e.g. "what have we learned about pricing across all our ideas?"), call `wiki_ingest` with `scope: { kind: 'org' }` and `source: { from_ideas: true }`. This rolls up across every idea wiki under the org rather than ingesting a single artifact. Org scope only — invalid with idea scope.

6. Tool Reference

5 tools, rendered live from the Gentic MCP manifest. Parameter tables come directly from each tool's JSON Schema.

7. Pricing

Pricing is pulled live from the Gentic MCP manifest. All prices are per call and deducted from your Gentic credits.

8. Notes

• All tools are organization-scoped — users only see their own wiki.
• Ingestion is **25¢ per call**. Querying, viewing, and linting are **free**.
• Source S3 keys must live inside the calling org and must not be wiki-layer pages — ingest raw artifacts, not the wiki itself.
• Concurrent ingests on the same scope race and last-write-wins on overlapping entities. Serialize per scope if you need consistency.
• `from_ideas: true` is org-scope only — it rolls up across all idea wikis under the org.
• Wiki pages are markdown under `orgs/{org}/wiki/...` and use `[[wikilinks]]` for cross-references. See WIKI.md for the full schema.