Choose an integration
All four options use the same project boundaries and the same allowlisted Genseo operations.
What is included in v1
- Public API access with project-bound API keys
- CLI login with browser authorization or a manual API key
- A hosted Streamable HTTP MCP server for Claude, Codex, Cursor, and other MCP clients
- A public plugin package shared by Claude and Codex
- Project inspection for the one project attached to the key
- 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
- Listing every project in a workspace
- Workspace-wide API keys
- 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
viewAsbehavior
Recommended API flow
- Create an API key in the app under Brand → API / Developer.
- Copy the Project ID from the same page.
- Call
GET /mefirst to confirm the key, project, and allowed capabilities. - Use only the project returned by
/me. - Create drafts before publishing.
- Ask the user before publishing unless the user has explicitly enabled autonomous publishing.
Base URL
Authorization header.
MCP endpoint
Never place API keys in an MCP URL, source file, public repository, screenshot, or chat message.

