canonical: https://jentic.com/apis/ai.seovendor.co/seo-gpt

# Ai Seovendor SEO GPT API

Jentic publishes the only available OpenAPI specification for SEO GPT API, keeping it validated and agent-ready. SEO GPT is an AI service that generates SEO content - titles, meta descriptions, page copy and other types - through a single content generation endpoint plus two helpers that enumerate the supported content type categories. Authentication is an apiKey passed as a query parameter (k or SEO_GPT_KEY) rather than a header, which is unusual but documented in the spec.

## For AI agents

Generate AI-powered SEO content (titles, meta descriptions, page copy) and look up the supported content type taxonomy through three endpoints.

## Scope

Does not handle keyword research, backlink data, or rank tracking - use for AI-driven on-page SEO content generation only.

## Capabilities

- Generate SEO-optimised titles, meta descriptions, and page copy for a target keyword
- Switch generation by content type - page copy, meta description, social copy, etc.
- Discover the available content type categories supported by the model
- List the specific content types available within a chosen category
- Tune output via parameters such as keyword, length, and tone within a single POST

## Use cases

### Title and Meta Description Generation

On-page SEO teams generate variants of titles and meta descriptions for landing pages by calling the content generation endpoint with the target keyword and the appropriate content type. The single POST endpoint handles all content variants, and the helper endpoints supply the valid content type values so an agent can validate input before calling.

Example prompt: POST /gpt-get-chrome.php with content_type=meta_description and keyword='electric bikes' and review the variants

### Long-Form Page Copy Drafting

Content teams use the same generator endpoint with the page_copy content type to produce a draft for a landing page. Because all generation is driven by a single endpoint, an agent can sweep across multiple keywords and content types programmatically without re-authenticating per call.

Example prompt: POST /gpt-get-chrome.php with content_type=page_copy and keyword='best wireless earbuds 2026'

### Content Type Discovery

Agents that need to enumerate the supported content types call POST /get_content_type_category to list the top-level categories and POST /get_gpt_content_type to drill into the content types within a category. This is helpful when the integration surfaces a UI dropdown or validates user input before sending it to the generator.

Example prompt: POST /get_content_type_category to list categories, then POST /get_gpt_content_type with the chosen category

### AI Agent SEO Drafting via Jentic

An agent built on Jentic can chain Ahrefs or Semrush keyword research with SEO GPT generation to produce a full briefed-and-drafted SEO asset. Jentic stores the SEO GPT key and applies it as the appropriate query parameter at request time, so the agent never sees the raw key in its context window.

Example prompt: Use Jentic to search 'generate SEO content', load the schema, and call with content_type and keyword for each target

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /gpt-get-chrome.php | Generate SEO content for a keyword and content type |
| POST | /get_content_type_category | List content type categories |
| POST | /get_gpt_content_type | List content types within a category |

## Key resources

- **Content** — Single POST endpoint that generates SEO content given a keyword and content type
- **Configuration** — Endpoints to enumerate content type categories and the content types within them

## Why Jentic

- **Setup:** Wiring the SEO GPT API by hand means passing its key as a query parameter and coding calls across its content generation and helper endpoints. Through Jentic you install once, import the SEO GPT API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** SEO GPT drives its generation and helper operations through the request body with no per-resource id, so limit the agent to the operations it needs, such as generating on-page content. You choose which operations are in the allowed set, so anything you leave out is not reachable.
- **Credential handling:** Your SEO GPT key is stored once, encrypted, by your own Jentic One instance and appended server-side at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'generate an SEO meta description', and Jentic returns the generator operation with its body schema, plus the helper operations to enumerate categories and content types, so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Agility Writer** — Long-form AI article generator with an async create-and-poll flow
- **Copy.ai** — AI copywriting platform with templated marketing content endpoints
- **OpenAI** — General-purpose LLM API with full control over prompts and parameters
- **Ahrefs** — SEO research API for keyword and backlink data
- **Semrush** — SEO and competitive research data feeding content briefs

## FAQ

### Why is there no official OpenAPI spec for SEO GPT API?

SEO Vendor does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the SEO GPT API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the SEO GPT API use?

The API uses an apiKey passed as a query parameter - either k or SEO_GPT_KEY. This is unusual compared to header-based auth and means the key can show up in proxy logs. Through Jentic, the key is stored in the credential vault and appended to the URL at execution time so the agent never sees it.

### What content types can the SEO GPT API generate?

Use POST /get_content_type_category to list the supported categories, then POST /get_gpt_content_type with a chosen category to enumerate the specific content types - typically titles, meta descriptions, page copy, and related on-page assets. Pass the chosen content type to the generator endpoint.

### How do I generate SEO content through Jentic?

Search Jentic for 'generate SEO content'. Load the POST /gpt-get-chrome.php schema, supply the keyword and content_type, and execute. Jentic appends the SEO_GPT_KEY query parameter from the vault and returns the generated content.

### What are the rate limits for the SEO GPT API?

The OpenAPI spec does not declare explicit per-second limits. Because the generator is LLM-backed, plan for second-scale latency per call and avoid tight loops; batch by serialising calls per keyword rather than firing concurrently.

### Can I generate multiple content types in one call?

No. The generator endpoint takes a single content_type per request. To produce a title and a meta description for the same keyword, issue two POST calls - they share a keyword and authentication so the cost is just one extra round trip.

### Can I limit what my agent is allowed to do with the SEO GPT API?

Yes. Jentic One is self-hosted, so you run it and your own rules decide which SEO GPT operations and credentials your agent can reach. The API exposes just three operations, all driven by the request body with no per-resource id: generating content via POST /gpt-get-chrome.php, listing content type categories, and listing content types within a category. You put only the operations the agent needs into the allowed set, so you can permit content generation while leaving out anything else, and any operation you do not include is not callable.