Gentic Brain — Documentation

1. Getting Started

Sign Up & Get Your API Key

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

1. Go to gentic.co/brain 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/brain. For Claude Code:

claude mcp add gentic-brain \
  --transport http \
  https://mcp.gentic.co/brain \
  --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 Brain 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/brain/SKILL.md

Or upload a .skill bundle to Claude Managed Agents:

https://gentic.co/brain/gentic-brain.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 capture a Slack thread, email, review, social mention, or note into the org's brain.
• User mentions "capture", "remember", "add to the brain", "file this", or "the agent should know about this".
• User wants to promote a previously-captured source into a permanent wiki entity page.
• User wants to undo a capture ("forget this", "un-capture", "remove that source").
• User asks "what does our brain know?" or wants a dashboard-style snapshot of recent captures and wiki activity.

5. Workflow

1. 1. Stage by canonical source_uri, always

   `wiki_stage_source` is the single mandated ingest path. Identify the source by its upstream's primary key — `slack://{channel}/{ts}` for Slack messages, `notion://page/{id}` for Notion pages, `email://{message-id}` for emails. Never use a title or human label that can drift. The `slug` is caller-provided (FR-028 — the system never auto-generates slugs from titles) and combined with `source_type` forms the logical identity. Re-staging the same `(source_type, slug)` overwrites in place and emits `source_restaged`.

2. 2. Pick the right source_type

   The `source_type` enum mirrors `vectorize_content` so chaining doesn't need a translation layer. Use `slack` for Slack messages and threads, `email` for emails, `review` for product/store reviews, `social` for tweets / TikTok / IG mentions, `creator_feedback` for influencer-program responses, `note` for internal notes (e.g. a researcher's hand-written observation), and `other` only when nothing else fits.

3. 3. Search before promoting

   Staged sources are searchable via `search_knowledge` in ~10–60s after staging. Use that to check whether the brain already has overlapping coverage before deciding to promote. `wiki_ingest_source` is the bridge from captured knowledge to a permanent wiki entity page — call it only when the source is worth that promotion, not on every stage.

4. 4. Promote with a scope

   `wiki_ingest_source` takes the original `source_uri` and a scope: `{ kind: 'idea', ideaSlug }` for an idea wiki or `{ kind: 'org' }` for the org-shared wiki. Default to the same scope the captured source belongs to. Idempotent — re-promoting on the same `source_uri` updates the existing entities in place (`was_created: false`). The response includes `entity_view_url`, `wiki_paths`, and `index_view_url` — surface these as clickable markdown links back to the user.

5. 5. Soft-delete on uncapture

   `wiki_unstage_source` takes the same `source_uri` originally passed to `wiki_stage_source` — callers don't need to track the slug separately. It marks all matching knowledge chunks `is_deleted = TRUE`, writes a `.deleted` sidecar at the staged S3 key (the original .md is preserved for audit), and emits a `source_unstaged` event. Idempotent — re-running on a deleted or never-staged URI returns `soft_deleted: false`.

6. 6. Read the snapshot in one round-trip

   `brain_status_snapshot` is free and aggregates counts, recents, and the 7-day event feed into a single response — exactly what the Brain dashboard panel in gentic-web renders. Agents can call it to answer 'what does the brain know about us?' without four separate reads. Returns `success: false` with an `error` string on per-org failure (e.g. unmapped org); plan for both branches in the consumer.

6. Tool Reference

4 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 — the auth context determines the org, never a tool argument.
• `wiki_stage_source` is **free**; chained vectorization charges its own per-chunk meter on completion. `wiki_ingest_source` (promotion) is **25¢**. `wiki_unstage_source` and `brain_status_snapshot` are **free**.
• Identity is `(source_type, slug)`. Re-staging the same logical source overwrites in place and emits `source_restaged` so the brain doesn't accumulate duplicates.
• Knowledge chunks are searchable ~10–60s after `wiki_stage_source` returns — the call itself is sub-second.
• `brain_status_snapshot` returns the last 7 days of brain events capped at 100. `truncated: true` signals the cap was hit.
• Sources soft-deleted via `wiki_unstage_source` keep their original markdown in S3 for audit; only knowledge chunks and the sidecar marker change.