Yes, on two different levels. Publicit runs a native Model Context Protocol server, so an AI assistant can check budgets and pacing, review metrics, inspect targeting and explore inventory in plain language. Separately, Publicit Ad-Exchange is RTB infrastructure normalised into OpenRTB-compatible formats and engineered for sub-5ms p99 bid response latency.
Publicit runs a native Model Context Protocol server, one of the first among advertising platforms, at https://www.dashboard.publicit.com/mcp over streamable HTTP.
Authentication is a Personal Access Token generated from Settings, then Developer. A token inherits only the permissions of the user who created it, only a SHA-256 hash is stored, and it can be revoked at any time.
Any MCP-compatible client works. Claude Desktop and Claude.ai connect as custom connectors; other assistants connect wherever they support remote MCP servers.
Publicit Ad-Exchange is real-time bidding infrastructure across CTV, DOOH, OOH and in-app inventory, normalised into OpenRTB-compatible formats so a compliant buyer needs no custom integration.
It is engineered for sub-5ms p99 bid response latency at the exchange edge. Currently in early access.
Publicit Global S.L. is a registered IAB Europe TCF v2.2 vendor, and publishes a sellers.json declaring the sellers it represents, so the supply chain is verifiable.
Payments are escrowed: an advertiser's charge is held rather than passed straight through, and released to the publisher once delivery has been evidenced and accepted.
The company is Publicit Global S.L., an independent company based in Barcelona. Details on the about page.
Teams have members with owner, admin and user roles, invited by email, with roles editable afterwards.
The fiscal address used for legal invoicing is snapshotted onto each invoice at issuance, so later edits never mutate past invoices. Each campaign payment produces its own invoice.