For AI agents
AdPrompt connects marketing intelligence, content, creative assets, advertising, and social workflows in one platform for businesses and agencies. Its public x402 gateway also makes selected marketing engines available to applications and AI agents on a pay-per-result basis.
What can an AI agent use?
The public engine catalog includes Brand Scan, Competitive Analysis, Social Presence Full Plan, Ad Strategy + Budget, Image Generator, Logo Generation, Video Generation 8s, Content Suggestor, and Color Palette Generator. Packages combine related engines into brand, campaign, and social-content workflows.
Use the live catalog for current products, package contents, required business context, and pricing. The gateway is a separate pay-per-call service; reading this page does not create an AdPrompt account, connect a wallet, or authorize a purchase.
REST API or MCP: two ways to connect
The REST API is for applications that send HTTP requests. The API reference describes the supported paths, request fields, examples, and responses. The downloadable OpenAPI JSON is the machine-readable contract for the same API.
MCP means Model Context Protocol. The AdPrompt MCP server exposes engines and packages as discoverable tools through stateless Streamable HTTP. Use an MCP client that supports x402 payments to execute paid tools. The browser MCP guide includes connection examples and the tool catalog.
The public developer website is https://x402.adprompt.ai/. The existing API resource base remains https://x402.adprompt.io/ for compatibility. Use the server URLs in the OpenAPI document and the MCP connection guide. The MCP protocol endpoint is https://x402.adprompt.io/mcp and accepts POST; opening /mcp in a browser shows the human-readable guide instead.
How do payments and results work?
Paid requests use x402, an HTTP payment protocol. An unpaid request returns a 402 Payment Required challenge. An authorized x402-compatible client supplies payment in USDC on Base before the gateway queues the work. Pricing comes from the live catalog and the actual payment challenge, not a fixed price copied from a marketing page.
Confirm the requested operation, business context, and spending authorization before purchasing. A wallet address alone is not permission to spend. Never share private keys, seed phrases, or internal API credentials in prompts or request bodies.
A successful paid request returns the documented queued response and result/report links. Use those links to retrieve the result; use job polling where the API specifies it. Reuse a documented idempotency key for supported retries, and do not blindly repeat paid requests. Creating a marketing asset is not the same as publishing it to an advertising or social account.
Where should an agent start?
Start with this guide to understand AdPrompt, then read the OpenAPI contract or MCP guide for the requested workflow. Check the live catalog before quoting a price or selecting a package. Supply only the input and business information required by the selected tool, and use the returned result links as evidence of what actually completed.
The x402 discovery document provides the gateway description, protocol, network, catalog URL, and supporting endpoints. The /llms.txt file on adprompt.ai provides a concise Markdown reference and links to primary public resources. Customer records, account administration, and private content are not exposed by this guide.
AdPrompt in search and AI answers
SEO means search engine optimization: helping people find relevant pages in search. AEO means answer engine optimization: making useful answers easy to understand and reference. GEO means generative engine optimization: presenting clear, reliable information that generative search systems can use as supporting context.
This guide provides visible text, descriptive links, and first-party product and developer references for people and automated readers. Use the public website for product context, and the API contract and live catalog for integration facts. Do not treat illustrative marketing demos as completed customer actions.
The llms.txt format is an emerging documentation convention, not an access-control file or a promise of search placement. Google says its established SEO practices remain relevant to AI features; no special AI text file guarantees crawling, inclusion, or citations.
Primary resources
- Developer console
- Browse engines and packages.
- API reference
- Read requests, schemas, examples, and responses.
- OpenAPI JSON
- The machine-readable API contract; the docs page also provides a download.
- MCP guide
- Connection examples and discoverable tools.
- Live catalog
- Current product and package pricing and business-context requirements.
- x402 discovery
- Protocol and endpoint discovery metadata.
Further reading: Google Search guidance for AI features and the llms.txt proposal.