Gentic Content — Documentation

1. Getting Started

Sign Up & Get Your API Key

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

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

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

Or upload a .skill bundle to Claude Managed Agents:

https://gentic.co/content/gentic-content.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 generate marketing copy, a blog post, email, or newsletter that sounds like their brand.
• User wants to teach the system their brand voice from examples of their existing writing.
• User wants an objective, checkable measure of whether a draft is on-brand.
• User wants drafts screened for AI 'slop', near-duplicates of source material, or unsupported claims before shipping.
• User wants to rebuild or update the brand's writing profile as their voice evolves.
• User wants to feed on-brand drafts into a review, CMS, or publishing workflow.

5. Workflow

1. 1. Build the corpus with `add_content_sample`

   Add examples of the brand's real writing — pass `text` (paste) OR a `url` to fetch (the article text is extracted and boilerplate stripped; review the returned preview). Tag each with its `content_type` (blog, email, newsletter, …). Both pasted and fetched samples need approval next. `add_content_sample` is **free**. List what's in the corpus with `list_content_samples` (free).

2. 2. Approve extractions with `approve_content_sample`

   Approve each captured sample so it becomes eligible to build a profile. Only approved samples of a given `content_type` feed that type's profile — so approve deliberately, and keep off-voice or low-quality pieces out. `approve_content_sample` is **free**.

3. 3. Build the profile with `build_writing_profile`

   Build (or rebuild) the writing profile for one voice + content type — **async, billed per build on completion (200¢)**. It runs anti-slop-first: filters the corpus to the slop-free subset, then computes the stylometric fingerprint + brand lexicon + on-voice calibration from that subset. Requires approved samples of that content type first. Returns a `job_id` — poll `get_content_jobs`, then read the result with `get_writing_profile` (free).

4. 4. Generate a draft with `create_content`

   Give it a brief. **Async, billed per shipped draft on completion (50¢)**. The writer generates candidates, ranks by stylometric fit, and gates on a two-family on-voice panel + anti-slop + near-copy + factuality. Requires an approved writing profile first. Returns a `job_id` — poll `get_content_jobs` for the draft, a checkable scorecard, and a `decision` (`auto_ship` / `needs_review` / `needs_profile_rebuild`).

5. 5. Poll async jobs with `get_content_jobs`

   Both `build_writing_profile` and `create_content` return a `job_id` immediately and run in the background. Poll `get_content_jobs` by id for `status` (pending / complete / failed), a `timed_out` flag, and the result. `get_content_jobs` is **free** — poll freely; you're only billed when the underlying build or draft completes.

6. 6. Act on the decision

   Read the scorecard and `decision`. `auto_ship` — the draft cleared every gate; present it and its scores. `needs_review` — surface the specific gate(s) it's borderline on so the user can decide. `needs_profile_rebuild` — the profile no longer fits (voice drift or too thin a corpus); add more approved samples and rebuild before generating again. Never present a draft as 'on-brand' without its scorecard.

6. Tool Reference

7 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

• Two billable meters, everything else free: `build_writing_profile` is **200¢ per build** and `create_content` is **50¢ per shipped draft**, both charged on completion. `add_content_sample`, `approve_content_sample`, `list_content_samples`, `get_writing_profile`, and `get_content_jobs` are free.
• Order matters: add samples → approve them → build a profile → generate content. `build_writing_profile` needs approved samples of that content type; `create_content` needs an approved profile.
• Async: profile builds and draft generations return a `job_id` and run in the background. Poll `get_content_jobs`; you're billed only when the job completes.
• One profile per voice + content type. Build separate profiles for, say, blog vs. email — each is scored on its own corpus.
• The profile is the objective scorer: stylometric fingerprint band + brand lexicon + on-voice judge threshold, built from the anti-slop clean subset. That's what makes 'on-brand' checkable rather than a matter of taste.
• `get_writing_profile` returns the current approved profile by default; pass `version`/`id` for a specific one, or `list=true` to see all versions.