Developer Platform Overview

The MaxAEO Developer Platform opens up the engine MaxAEO uses to collect AI answers so your own code can use it: you submit a question and a target platform, we ask that platform for real, and return the AI’s raw answer, cited sources, and share link — plus the reasoning steps and video/image cards when the platform provides them.

Common use cases:

Build your own AI search monitoring: send brand-related questions to AI platforms on a schedule, and track in your own data warehouse whether your brand is mentioned and which pages get cited.
Validate content and GEO work: after publishing, check directly whether AI answers cite your pages (the cited field).
Research and analysis: collect answers to the same question across platforms and compare viewpoints, sources, and answer structure.
Give your AI agent an “ask another AI” tool: connect over MCP so clients like Claude Code and Cursor can call it directly.

Two ways to integrate

	Open API	MCP server
Best for	Your backend services, scripts, data pipelines	AI clients and agents that support MCP
Protocol	HTTPS + JSON, always `POST`	MCP Streamable HTTP (stateless)
Capabilities	List platforms, submit tasks, retrieve tasks, list tasks	The same four, exposed as 4 tools
Authentication	`Authorization: Bearer <API key>`	Same
Billing & rate limits	Credits charged per successful task	Identical to the open API

Both share the same API key, the same credit balance, and the same rate limits.

Build with an AI coding assistant

When you write integration code with an AI coding assistant such as Claude Code or Cursor, give it maxaeo-api.md. It’s an integration guide written for AI: the basics, the fields of the four endpoints and the task object, error codes, the rules that are easiest to get wrong, and ready-to-run Python / Node.js reference implementations. The file doesn’t contain or need your API key.

The file starts with Agent Skill name / description metadata and the rest is plain Markdown, so you can install it as a skill or use it as an ordinary document.

Download maxaeo-api.md

Install it as a skill — pick one:

# This project only (can be shared with your team through the repo)
mkdir -p .claude/skills/maxaeo-api && curl -fsSL https://maxaeo.ai/docs/developers/maxaeo-api.md -o .claude/skills/maxaeo-api/SKILL.md

# All your projects
mkdir -p ~/.claude/skills/maxaeo-api && curl -fsSL https://maxaeo.ai/docs/developers/maxaeo-api.md -o ~/.claude/skills/maxaeo-api/SKILL.md

From then on, when you ask Claude Code to call the MaxAEO API or set up MCP, it loads the skill automatically based on its description.

Save it in your project:

mkdir -p docs && curl -fsSL https://maxaeo.ai/docs/developers/maxaeo-api.md -o docs/maxaeo-api.md

Then add a line to AGENTS.md (or your tool’s rules file):

- Before calling the MaxAEO API or MCP server, read docs/maxaeo-api.md and follow its "Rules you must follow".

Tools that support Agent Skills can also use it as maxaeo-api/SKILL.md in their skills directory.

For more detail, every Developer Platform page is also merged into one text file, developer-platform.txt, which you can hand to an AI in full.

How it works: asynchronous tasks

An AI platform typically takes anywhere from tens of seconds to two minutes to generate an answer, plus any time spent in the queue, so the API is asynchronous:

Submit a task: call Submit a Task with a platform and a question. You get a task_id back immediately, with status queued. Credits for that platform’s price are reserved at submission.
Poll for the result: call Retrieve a Task about every 15 seconds until the status becomes succeeded, failed, or canceled.
Read the result: on success, read the answer and cited sources from answer and raw_result, and the credits are charged at the price locked in at submission. Failed or canceled tasks are free — the reserved credits are released.

The full state flow is covered in Task Lifecycle.

At a glance

Item	Value
API Base URL	`https://maxaeo.ai/geoapi/geodata/developer`
MCP endpoint	`https://maxaeo.ai/geoapi/geodata/developer/mcp`
Authentication	Request header `Authorization: Bearer gdev_…` — see Authentication
Request format	Every endpoint is `POST` with a JSON object body
Response format	`{"ret": 1, "data": {"ent": …}}`; any `ret` other than 1 is an error — see API Overview
Developer Console	maxaeo.ai/developers: create API keys, try requests in the Playground, view logs and usage

The Developer Platform uses the same account as the MaxAEO product — sign in to the console the same way you sign in to MaxAEO.

Developer Console pages

Console page	What it’s for	Docs
Overview	Quickstart progress, credit balance, last 7 days of requests, platform status	This page
APIs & Platforms	Supported platforms, their status, and 24-hour success rate and latency	Platforms, Priority & Country
Playground	Send requests without writing code, inspect the response, and copy the calling code	Playground
API Keys	Create, disable, roll, and delete API keys	Manage API Keys
Request Logs	Per-request details: status, errors, and responses	Logs & Usage
Usage	Credit balance, consumption, success rate, quotas and limits	Logs & Usage
Pricing	Per-platform prices for both tiers, and billing rules	Billing & Credits

Start here

QuickstartCreate an API key, send your first request, and get an AI answer in about five minutes.

AuthenticationHeader format, what a key can access, and security best practices.

API ReferenceParameters, responses, and error codes for the four open API endpoints.

Connect via MCPCall it directly from Claude Code, Cursor, VS Code, and other clients.

Working with ResultsMake sense of the answer text, cited sources, reasoning steps, and media cards.

Billing & CreditsHow credits are reserved, charged, and released, and how to estimate costs.