Publink lets AI agents create ads, find publisher inventory and run advertising campaigns, while people approve budgets and key decisions.
Agents connect through the Ad Context Protocol (AdCP) over MCP. Publink is built on ad-serving infrastructure and works across CTV, in-app, web and audio.
AdCP is an open standard that lets AI agents discover, buy and manage advertising in a common language. A buyer agent and a seller agent use the same set of tasks: find products that fit a brief, create and update a buy, send creatives and read delivery.
AdCP is maintained by AgenticAdvertising.org. Publink is a member and runs an AdCP sales agent.
A person gives the agent a brief: the goal, the budget, the dates and the audience. With Publink, agents draft the ads, including video, propose media from inventory that publishers have opened, and prepare a campaign plan.
A person approves the creative, the media plan and the spend. Then the agents launch the campaign, manage delivery within the limits that were approved and read the results from the campaign record.
Yes. MCP (Model Context Protocol) is an open standard for connecting AI agents to outside tools. Publink offers an AdCP sales agent over MCP at https://mcp.publink.io/mcp.
Through it, an agent can find inventory, create a campaign, create ads and read results. Access is set up with the Publink team. Write to [email protected] to get started.
Publishers choose which inventory they open to agents and keep control of buyers, floors and selling rules. Floors, priorities, blocks and caps apply before any buyer sees a request, whether the buyer is a person, a DSP or an agent.
An impression bought by an agent gets the same records as any other: what was declared, what was paid and the reason for every miss.
Through an AdCP sales agent. The inventory a publisher chooses to open is described so buying agents can find it, understand it and propose against it. The publisher's rules and approvals still apply before anything runs.
Publishers can also host an adagents.json file, which says which agents are allowed to sell their inventory.
Not with Publink. Agents prepare almost everything and manage delivery, but committing budget, publishing creative and changing live terms wait for a person.
An agent sees and changes only what its account allows, and creatives and plans wait for the approvals the account requires.
If you are building an agent that buys media, it can connect to Publink through supported AdCP tasks over MCP. Tell the Publink team what your agent does, and they set up access and walk your team through the integration.
Your agent then works inside the limits a person set, such as account permissions, review steps and budgets.
CTV, in-app, web and audio. One brief can become one campaign, with ads cut for the TV, the phone, the browser and the podcast.
OpenRTB handles the real-time auction for a single impression, in milliseconds. AdCP handles the work around the campaign: discovery, buying, creatives and reporting, over seconds to days.
They work together. Publink supports both, along with VAST, sellers.json and SupplyChain.
Publink checks the declared supply path against available sellers.json, ads.txt and SupplyChain evidence, and flags missing or inconsistent entries.
For agents, adagents.json lets a publisher say which agents may sell its inventory, and buyers can confirm who they are talking to.
Publink was founded by Shay Levy, who has nearly 10 years in adtech building and operating ad-serving and programmatic advertising systems.
Publink is a member of AgenticAdvertising.org, the community behind AdCP. Publink (publink.io) is a separate company from Publink sp. z o.o. (publink.com).