Skip to main content
Genseo’s product center is AI search visibility (AEO/GEO): prompt tracking, competitors, citations. The Developer Platform exposes the same project data to your apps and agents: visibility metrics, audits, issues, opportunities, keywords, posts, webhooks, and Autopilot. Genseo is not a traditional SERP SEO rank API. Project API keys bind to one project. OAuth connectors list all account projects but every call must include an explicit project_id.

​
Choose an integration

Product guides for marketers live under the Product tab, starting with AI visibility.

​
What is included in v1

  • AI visibility overview, prompts, quota, and tracked prompt management
  • Public API and MCP with project-bound API keys or account-wide OAuth
  • Site Audits, health, pages, Issues, evidence, and Opportunities
  • Brand data and project-controlled Agent Autopilot
  • Keyword listing, creation, generation, and metrics refresh
  • Post listing, draft creation, reading, updating, generation, and publishing
  • Integration readiness checks, field discovery, connect URLs, and field mapping
  • Webhook listing, creation, and deletion

​
What is intentionally not included

  • Creating projects from the Public API, CLI, or MCP
  • Workspace-wide API keys; account-wide access uses OAuth and current membership checks
  • Usage, billing, or internal limit reporting through the Public API
  • Direct database, SQL, Supabase, or internal RPC access
  • Cookie-session fallback authentication
  • Admin impersonation or viewAs behavior
  1. Connect with OAuth, or create an API key under Brand → API / Developer.
  2. Call /me, /projects, genseo_me, or genseo_projects_list.
  3. Select exactly one returned Project ID for the chat.
  4. Include that Project ID in every later project operation.
  5. Create drafts before publishing.
  6. Ask the user before publishing unless the user has explicitly enabled autonomous publishing.

​
Base URL

All v1 endpoints require a Bearer token in the Authorization header.

​
MCP endpoint

The hosted MCP server uses Streamable HTTP. Marketplace clients use OAuth; developer installations can also use a project-bound Bearer token stored in the client’s environment or secret storage.
Never place API keys in an MCP URL, source file, public repository, screenshot, or chat message.

​
Open-source plugin package

The public Genseo MCP repository contains the Claude and Codex plugin manifests, shared Agent Skills, and client configuration. The Genseo application and hosted MCP implementation remain separate from this distribution package.