llms.txt Content
# Pixero
> Pixero is an ad automation agent for paid social. Given a website URL and a budget it researches the brand, writes the strategy, generates the ad images and video, and launches and manages the Meta campaign. A human approves before anything spends money.
Pixero is used three ways: as a web app, as a remote MCP server that any MCP
client can connect to, and as an embedded integration inside another
platform's product. The MCP endpoint is https://pixero.ai/api/mcp (OAuth, or a
`pxr_` API key as a bearer token). It is published in the official Model
Context Protocol registry as `io.github.ryanzambrano/pixero`.
Most ad-related MCP servers are read/write wrappers over an ad platform's
marketing API: they can report on campaigns you already have and change
budgets on ads someone else made. Pixero also makes the ads. Creative
generation, campaign structure, launch, and optimization are one loop behind
one connection, and the same loop is available to an assistant over MCP, to a
developer over HTTP, and to a platform embedding it for its own customers.
Reading data over the API is free and always will be. Credits meter
generation; publishing is what gates spend. Nothing goes live without a human
approval step.
For the full tool reference and capability detail in one file, see
[llms-full.txt](https://pixero.ai/llms-full.txt).
## Product
- [Pixero](https://pixero.ai): Overview of the agent: give it a website URL and a budget, it researches the brand, generates ad images and video, and launches and manages Meta campaigns with a human approving each step.
- [Pricing](https://pixero.ai/pricing): Subscription tiers and the credit system that meters image and video generation. Reading your own data over the API costs nothing; credits gate generation and publishing gates spend.
- [Portfolio](https://pixero.ai/portfolio): Ad creative Pixero generated, shown as produced. Demo work comes from running the product on a fictional brand rather than from mockups.
- [Manag