pubexchange_ by openserve
A publisher's agent, acting for its ownerfree · no card
Build audiences from a site's own visitors
Save an audience over the owner's own visitors and known people: opened a section, showed intent, came back, lapsed, or came from named companies. Read its size, then send it to the owner's own connected ad account.
- identity:read
- identity:write
/ 01 paste this into your agent
Set up PubExchange for me. The job: Build audiences from a site's own visitors. Read https://www.openserve.com/llms.txt and follow it to connect in this client. The key needs these scopes: identity:read, identity:write. Tell me exactly what I need to do on my side, then call get_account and tell me what is left of the free allowance.
/ 02 or connect it yourself
# scopes for this job: identity:read identity:write claude mcp add --transport http openserve https://www.openserve.com/api/v1/mcp \ --header "Authorization: Bearer <key>"
The free account includes 1,000 agent calls and needs no card. get_account says what is left and is never counted.
the tools for this job
- create_audience
- a rule in, a saved audience and its size out
- list_audiences
- each audience's rule in words, people and browsers
- sync_audience_to_channel
- to the owner's own Meta or Google; waits for approval
the agent, at work
> create_audience {"name":"Pricing readers","rule":{"kind":"visited","pathPrefix":"/pricing","days":30}}
< saved · marked as made by an agent · people and browsers in it today
> sync_audience_to_channel {"audienceId":"…","channel":"meta"}
< state waiting · waitingForApproval true
> sync_audience_to_channel {"audienceId":"…","channel":"meta"} (after approval)
< state on · re-sent dailythe person's side
What your person sees: the Audiences card
- Pricing readers · made by an agent
- 1,930 people
- Lapsed 60 days
- 4,212 people
- Meta · Pricing readers
- Waiting for you
An example with sample values.
what an agent cannot do here
- the first send of a list waits for a person on the Audiences card
- only people who gave this business their email are sent, hashed
- sizes only; never names or emails. A workspace keeps at most 50 audiences
also asked for as
- first-party audience API
- retargeting audiences from website visitors
- custom audience sync for an agent
- suppression list of existing customers



