Open platform
Your proof, in your stack.
API, webhooks and MCP. Verified plays and screen health land in the tools you already run, not in one more dashboard to log into.
An open platform, not a walled garden. Your data is never locked in.
A Harvester read off the glass, matched to the play.
{
"playId": "cmh2v8q1k0004vojo9x2c7d1e",
"organisationId": "org_meridian",
"screenId": "scr_8kUq2",
"creativeId": "cre_Vt91x",
"externalPlayId": null,
"t0": "1761735600",
"events": [
{
"type": "HARVESTER",
"createdAt": "1761735601",
"fingerprint": "fp_3af9c1e07b",
"deviceKey": "02:de:00:00:02:04",
"matchedAt": "1761735604",
"matchRuleVersion": "play-match@1"
}
]
}The walled garden
A dashboard is not infrastructure
Proof that lives only in a vendor's portal is a report you go and read. Proof that lands in your own systems is something you can price, gate and act on without logging in anywhere.
One more login
Another portal your team has to remember to check, alongside the six they already have.
Nothing downstream
The numbers cannot reach your reporting, your billing or the exchange you sell through.
And not portable
When the data only exists in someone else's tool, switching costs become the product.
Go and read it
Someone has to do this every time they want to know.
- Log in
- Filter
- Export
- An out-of-date file
It comes to you
You set it up once and it runs on its own.
- Play verified
- Event
- Your systems
Both give you the same numbers. The difference is when you get them. A report is only as current as the last time someone exported it. An event arrives when the play is verified, so your own systems can act on it without anyone logging in.
Three ways out
API. Webhooks. MCP.
Verified delivery leaves Vojo the moment it happens. Pick the surface that fits your stack, or use all three.
API
Read your sites, screens and harvesters, plus the verified delivery behind them. The same data the portal renders.
Auth and setup: Organisation key, scoped to your own organisation
Status: Live
Webhooks
Events pushed to your endpoint the moment they happen. Subscribe only to the ones you need.
Auth and setup: Self-serve in the portal: add an endpoint, pick events
Status: Live
MCP
The only verification MCP that lets you view your campaign's delivery in real time from your favourite AI tools.
Auth and setup: Talk to us to connect
Status: Early access
What flows out
The events, and where teams send them
Named product events, not opaque partner blobs. Each carries verified delivery or live screen state, and each is something you can route, store and act on.
Verified plays
- verification.score
- verification.ping
- verification.pod
Carries
The play, its screen and creative, and what each layer saw: Passport reporting from inside the ad, the Harvester's read off the glass, then the settled vTrust Score and band.
Where teams send it
Exchanges and SSPs can attach it to the impression record, so a buyer query is answered from the source. BI and warehouses report on evidence, not estimates.
Screen health & quality
- screen.activity_changed
- screen.quality
- screen.calibrated
Carries
Screen on or off, with the time it changed. Brightness and per-channel colour measured against the screen's calibration baseline, and when that baseline is reset.
Where teams send it
Ops and alerting, so a dark or drifting panel raises the alert your team already responds to, before a client notices.
And many more…
Building your own reporting? Read the estate through the API, subscribe to what changes, and model it in your own warehouse and BI layer, or connect an MCP client for agent workflows.
Never locked in
Your data, never locked in.
Because Vojo doesn't sell your inventory or sit in your demand chain, the data flows the way you want it to, out to your stack, on your terms. Leaving is always as open as arriving.
It leaves as it happens
Verified plays and screen health are pushed to your endpoint at the moment they occur, so your copy is current rather than exported.
And it stays yours if you leave
The record sits in your systems, in your format. Nothing about the verification depends on you continuing to log in here.
A platform that keeps your evidence hostage is a platform you cannot use as evidence.
See the events from your own screens arrive in a demo.
Questions
What developers ask first
- How do I authenticate?
- With an organisation key. It scopes every read to your own organisation, so a key can only ever see your own sites, screens and harvesters.
- How do I set up webhooks?
- In the portal, yourself. Point an endpoint at the events you care about and they start arriving, with no integration call and no waiting on us to enable anything.
- What can I read through the API? Do I need the portal at all?
- Your sites, screens and harvesters, plus the verified delivery behind them. It is the same data the portal renders, which is deliberate: there is no richer internal view we keep back. Everything the portal shows is reachable through the API and pushed through webhooks, so you can run Vojo from your own systems.
- What is the MCP server for?
- It's the only verification MCP that lets you view your campaign's delivery in real time from your favourite AI tools, and agent workflows reach the same estate and delivery data without anyone hand-rolling a wrapper around the REST API. It is early access: talk to us before you build something load-bearing on it.
- Is there developer documentation?
- Full developer and integration documentation is on the way. Until then, webhooks are self-serve in the portal, and we walk technical teams through the API and MCP in a demo.
- What happens to the integration if I stop paying?
- The data you already pulled is yours and stays in your systems. That is the point of pushing it as it happens rather than holding it for export. Live access ends with the account, as you would expect.
Open platform
Your proof. Your systems.
API, webhooks and MCP, so verified delivery reaches the tools you already run instead of waiting in a dashboard.
Webhooks self-serve · MCP early access