Advertisers
Demand partners
Demand partners bring buyer demand to Visor over an OpenRTB-style connection, with fields agreed at onboarding and not published here. Billing is in US dollars.
On this page
Demand partners bring buyer demand to Visor. Visor is the ad network (SSP) for AI chat apps, for US traffic only. SSP means supply-side platform: Visor sits between those apps and the buyers. A connection starts with a note, then a call and a contract. The form does not start bidding.
This page is for DSPs, ad networks, and agencies that bring demand. A DSP is a demand-side platform, the system a buyer uses to bid. The terms call the same group ad networks, DSPs, and similar buyers. The product page is Partners.
Who this page is for
The inventory is US chat apps that passed a traffic check. One labeled ad sits after the answer. How it works is the path.
About 10 million US users are monetized on the network.1
1 Our network currently monetizes about 10 million users, all in the US. People in apps that passed review, as of November 2026. Not a count of apps.
Publishers do not take an intro call. Demand partners do. The publisher guidelines draw that line on purpose. Your path is the note, the call, and the contract.
How a connection works
There are three ways to connect. Pick the one that matches how you buy. The fields are agreed before traffic. The server path is OpenRTB-style: a request after the answer, and a bid or no bid.
| Path | What happens |
|---|---|
| Server-to-server | We send a bid request after the answer. You return a CPM in US dollars and a creative, or no bid. The fields are in the contract. The shape is OpenRTB-style. |
| SDK mediation | Your SDK can compete for the slot the app already renders. The slot stays labeled and after the answer. |
| Direct deal | A placement and a CPM are written down before traffic runs. |
There is no sample request here. The exact fields are agreed at onboarding. They are not written on the public site.
What is on the request
A request carries coarse context. Country, device class, topic, and intent. That is the set we pass. Country means the United States. It is not a named audience.
The publisher may send Visor a wider set for matching: the current conversation or a short topic summary, anonymized in-app signals, device type, country, an under-18 flag, and a pseudonymous identifier. That wider set is not what a demand partner receives. You do not receive the raw chat.
What you never receive
No user data passes in either direction, beyond the coarse context fields. We do not take the forbidden fields back from you either. A creative and a CPM are the response. A person is not.
- No name, email address, or phone number.
- No precise location.
- No third-party cookie.
- No raw chat.
- No payment data, government ID, or password.
- No list of people, and no cross-site profile.
We do not sell personal information. Advertisers and demand partners get delivery and spend in US dollars, not a list of people. The privacy policy is the source. Under the CCPA and the CPRA, we do not sell personal information, and we do not share it for cross-context behavioral advertising.
You have to be able to run without user-level data. A buyer that needs a cookie, a retargeting list, or a person’s identity is not a fit for this inventory.
What you send back
On the server path, the response is a CPM in US dollars and a creative, or no bid. On a direct deal, the CPM and the placement are written down before traffic. Either way, the creative follows the ad content policy. It stays labeled. It does not imitate the assistant, a system message, or a public agency.
Refused categories stay off. The list is the ad policy, and Campaign review repeats it for buyers who bring their own creative. One ad can show after the answer. If nothing qualifies, nothing shows. You do not get a second slot to fill.
- Creatives stay labeled Ad · Sponsored and do not imitate the assistant.
- Refused categories stay off.
- The price you return is a CPM in US dollars, or you return no bid.
- You can run without user-level data.
Billing
Billing is in US dollars. Who invoices whom, and when, is in the agreement. There is no public rate card. Up to $180 CPM is the publisher ceiling, not an offer to you.
Payments is the longer page for currency, statements, and the contracting entity. You contract with Securax UG. The agreement sets the invoice path. No rate, minimum, or net term is published here.
How to start
Demand partners go live only after an intro call, an NDA, and a technical integration. We can say no. The terms state that gate next to the publisher and advertiser gates. Publishers go live after a traffic check. Advertisers go live after campaign review. Your gate is the call and the contract.
Send the note
Use the form on Partners. A person reads it. Say what you want to buy. The form does not start bidding.
Take the call, if the inventory fits
The next step, if the inventory fits, is a call and a contract. If it does not fit, we say so. There is no public waitlist and no promise of a clock time.
Sign the NDA and the agreement
The matching method, the bidding logic, and the field list wait for that paperwork. The data boundary on this page is already public. The method is not.
Integrate, then traffic
Technical integration follows the contract. Fields are the ones you agreed, not a sample from the public docs. Bidding does not start from the form.
ads.txt and sellers.json
Buyers often ask for an ads.txt line, a sellers.json file, and a SupplyChain node before they bid. Visor has not published those yet. ads.txt and sellers.json explains the specs and the current status. Do not add a Visor line until it is issued. Do not look for a sellers.json URL. Do not guess a schain node.
Publishers host ads.txt or app-ads.txt on their own domain, once they have a line. sellers.json, when it exists, is published by the ad system, not by each app. Neither file is a substitute for the contract.
What stays under NDA
The public half is the country, the device class, the topic, the intent, the ad policy, the quality bar, and reporting in views and US dollars. The contract half is the method.
| Public on this site | Under NDA or in the contract |
|---|---|
| US traffic in apps that passed review | Model architecture, features, and weights |
| Coarse fields: country, device class, topic, intent | The bidding logic |
| The ad policy and the quality bar | The numeric score on one impression |
| Reporting in views and US dollars | The exact OpenRTB fields, agreed at onboarding |
| Billing in US dollars, with no public rate card | Who invoices whom, and when |
Shared after the contract, not on this page. The traffic check is the public quality bar for supply. We do not publish every test in the check.