gentic

Gentic Landing Pages — Documentation

Let any AI agent design, deploy, and manage landing pages — live at {org}.gentic.run — with built-in lead capture, analytics, and CSV export. No code editors, no hosting config, no CMS. Just describe what you want and ship it.

1. Getting Started

Sign Up & Get Your API Key

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

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

claude mcp add gentic-landing-pages \
  --transport http \
  https://mcp.gentic.co/landing-pages \
  --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 Landing Pages 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/landing-pages/SKILL.md

Or upload a .skill bundle to Claude Managed Agents:

https://gentic.co/landing-pages/gentic-landing-pages.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 create a landing page, splash page, or coming-soon page.
  • User wants to deploy a page to a live URL without setting up hosting.
  • User wants to clone or remix an existing web page as a landing page.
  • User wants to collect email leads from a landing page.
  • User wants to query or export leads collected from their pages.
  • User wants to update the content of a live landing page.

5. Workflow

  1. 1. Fetch a reference page with `fetch_rendered_page` (10¢/call)

    Renders the target URL with full JavaScript execution and returns the complete DOM HTML. Use this when the user wants to clone or draw inspiration from an existing page. The rendered HTML can be passed directly to `deploy_landing_page` after modification. Unlike plain fetch, this captures SPAs, dynamic content, and JS-rendered layouts.

  2. 2. Deploy with `deploy_landing_page` ($7.50/call)

    Provide a `slug` (lowercase, alphanumeric + hyphens, 3–64 chars), a `title`, and complete self-contained `html`. The page goes live immediately at `{org-slug}.gentic.run/{slug}`. Optionally include `description` for metadata and `reference_url` for provenance tracking. The HTML must be a complete document — inline all styles and scripts, no external dependencies that might break.

  3. 3. Update live pages with `update_landing_page` ($7.50/call)

    Pass the `page_id` and any combination of `html`, `title`, or `description` to update. Only the fields you include are changed — omit `html` to update just metadata. The page redeploys to the same URL instantly. Use this for A/B testing copy, fixing typos, or iterating on design.

  4. 4. List pages with `list_landing_pages` (free)

    Returns all pages for the organization with metadata and lead counts. Pass `include_deleted: true` to see soft-deleted pages. Use this to check what's currently deployed before creating new pages or to find page IDs for other operations.

  5. 5. Query leads with `get_landing_page_leads` (free)

    Pass a `page_id` to retrieve collected email leads in reverse chronological order. Supports `limit` (default 100, max 500) and `offset` for pagination. Use this to review lead quality inline or to check submission volume.

  6. 6. Export leads with `export_landing_page_leads` (free)

    Returns a signed CSV download URL that expires in **1 hour**. Pass `page_id` to export leads from a specific page, or omit it to export leads across all pages. Mention the 1-hour expiry to the user.

  7. 7. Delete pages with `delete_landing_page` (free)

    Soft-deletes a page — removes it from public hosting but **preserves all lead data**. Leads remain queryable and exportable after deletion. Use this when a campaign ends or a page needs to be taken down.

  8. 8. Lead capture REST endpoint (not an MCP tool)

    Deployed pages can submit leads to `POST /api/leads/:orgSlug/:pageId` with a JSON body containing `email` (required) and optional `name`, `source`, and `metadata` fields. This endpoint is built into the hosting infrastructure — it's not called via MCP but should be referenced when building page HTML with forms.

6. Tool Reference

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

delete_landing_page

Free

Remove a landing page from public hosting. Lead data is preserved and still queryable.

ParameterTypeDescription
page_id
required
string

Page ID to delete

deploy_landing_page

750¢ / call

Deploy a landing page to a live URL at {org-slug}.gentic.run/{page-slug}. Provide the complete HTML content, a URL slug, and a title. The page will be publicly accessible immediately.

ParameterTypeDescription
slug
required
string

URL path segment (lowercase, alphanumeric + hyphens, 3-64 chars)

title
required
string

Page title for display and metadata

html
required
string

Complete, self-contained HTML document for the landing page

descriptionstring

Brief description of the page's purpose

reference_urlstring

Original reference URL used for generation

idea_slugstring

Idea slug to pull brand style guide from. If provided, injects the idea's brand CSS into the page.

ignore_brand_style_guide
required
boolean

Skip injecting the brand style guide CSS into this page (default: false)

default: false

export_landing_page_leads

Free

Export collected leads as a downloadable CSV file. Returns a signed URL that expires in 1 hour.

ParameterTypeDescription
page_idstring

Specific page ID (if omitted, exports leads from all pages)

fetch_rendered_page

10¢ / call

Fetch a web page with full JavaScript rendering and return the rendered HTML source code. Use this to capture the structure and content of a reference landing page for cloning — unlike fetch_page which returns only text, this returns the full rendered DOM.

ParameterTypeDescription
url
required
string

URL to fetch and render

get_landing_page_leads

Free

Query collected leads (email submissions) for a specific landing page. Returns results in reverse chronological order with pagination.

ParameterTypeDescription
page_id
required
string

Page ID to query leads for

limitnumber

Max results (default: 100, max: 500)

max 500 · default: 100

offsetnumber

Pagination offset (default: 0)

default: 0

list_landing_pages

Free

List all landing pages for the organization with metadata and lead counts.

ParameterTypeDescription
include_deletedboolean

Include deleted pages (default: false)

default: false

save_brand_style_guide

Free

Save or update a brand style guide for a specific idea. Sets brand colors, fonts, and tone that are automatically applied to future landing pages. You can set individual fields — any field you omit keeps its current value (if a guide already exists).

ParameterTypeDescription
idea_slug
required
string

The idea this style guide belongs to

primary_colorstring

Primary brand color (hex, e.g. '#2D5A3D')

secondary_colorstring

Secondary brand color (hex)

accent_colorstring

Accent brand color (hex)

primary_color_namestring

Name for the primary color (e.g. 'Forest Green')

secondary_color_namestring

Name for the secondary color

accent_color_namestring

Name for the accent color

heading_fontstring

Font family for headings (e.g. 'DM Serif Display')

body_fontstring

Font family for body text (e.g. 'Inter')

voicestring

Brand voice description (e.g. 'Warm, approachable, and confident')

personality_traitsstring[]

Personality trait keywords (e.g. ['friendly', 'minimal', 'bold'])

visual_moodstring[]

Visual mood keywords (e.g. ['warm', 'organic', 'handcrafted'])

logo_directionstring

Logo direction notes

update_landing_page

750¢ / call

Update an existing landing page's HTML content and/or metadata. Redeploys to the same URL.

ParameterTypeDescription
page_id
required
string

Page ID to update

htmlstring

New HTML content. If omitted, existing content is unchanged.

titlestring

New title

descriptionstring

New description

idea_slugstring

Idea slug to pull brand style guide from. If provided, injects the idea's brand CSS into the page.

ignore_brand_style_guide
required
boolean

Skip injecting the brand style guide CSS into this page (default: false)

default: false

7. Pricing

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

ToolCost
delete_landing_pageFree
deploy_landing_page750¢ / call
export_landing_page_leadsFree
fetch_rendered_page10¢ / call
get_landing_page_leadsFree
list_landing_pagesFree
save_brand_style_guideFree
update_landing_page750¢ / call

8. Notes

  • Pages are deployed to `{org-slug}.gentic.run/{page-slug}` — the org slug comes from the authenticated organization.
  • HTML must be **complete and self-contained** — inline all CSS and JS. External resources may break or load slowly.
  • Lead capture is built in. The REST endpoint `POST /api/leads/:orgSlug/:pageId` accepts `email` (required), `name`, `source`, and `metadata`.
  • Soft-deleted pages preserve all lead data — leads remain queryable and exportable.
  • Export CSV download links expire in **1 hour**.
  • Slugs must be lowercase, alphanumeric with hyphens, 3–64 characters, and cannot start or end with a hyphen.
  • All tools are organization-scoped — users only see their own pages and leads.