Ai Seovendor SEO GPT API
★ Only Publicly Available OpenAPI DocumentMarketingSeo SemapiKey3 EndpointsREST
For Agents
Generate AI-powered SEO content (titles, meta descriptions, page copy) and look up the supported content type taxonomy through three endpoints.
Use for: Generate an SEO meta description for the keyword 'electric bikes', I want to draft three SEO title variants for a product page, Create page copy targeted at 'best running shoes for flat feet', List the SEO content type categories supported by the API
Not supported: Does not handle keyword research, backlink data, or rank tracking — use for AI-driven on-page SEO content generation only.
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.
Install Jentic One Beta
Connect the SEO GPT API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SEO GPT API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with SEO GPT API.
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
Patterns agents use SEO GPT API for, with concrete tasks.
★ 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.
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.
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.
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.
Use Jentic to search 'generate SEO content', load the schema, and call with content_type and keyword for each target
Key Endpoints
3 endpoints — jentic publishes the only available openapi specification for seo gpt api, keeping it validated and agent-ready.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Because SEO GPT keys travel as query parameters, exposure risk is higher than header-based auth. Jentic isolates the key in its vault and appends it server-side at call time, so the raw key never reaches the agent transcript or browser-style logs.
Intent-based discovery
Agents search by intent (e.g. '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.
Time to first call
Direct integration: half a day to wire query-string auth and the two-step content type lookup. Through Jentic: under 30 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using SEO GPT API through Jentic.
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 at https://app.jentic.com/sign-up.
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.
GET STARTED