Placement verification

You paid for the placement. Relio proves it went live.

Automatic verification for creator deals: each agreed post, video or stream is found on the platform, matched against the contract — your code, your link — and kept as evidence that doesn't disappear when the post does.

  • Append-only evidence record
  • Deletion checks at +24h and +7d
  • Every breach verdict is made by a person
Verified3 Jul, 19:04

“New editor walkthrough is up — code MAKERS20 takes 20% off the annual plan, link's in the description.”

promo codeMAKERS20found in text
affiliate link/r/makers20found in links
snapshot #a91f4c re-checked +24h ✓ +7d ✓
The verification record — example data.

Your stack can't answer this question.

Your affiliate platform

Counts clicks and conversions through your links. It cannot tell you whether the post exists.

Influencer platforms

Work when the creator connects an account on the big social networks. Where your creators actually live, they see nothing.

Brand listening

Counts mentions across the web. A mention is not a contract, and it can't be tied to one.

Relio verifies the deliverable itself. And it is the only tool that reaches Telegram, Twitch and Kick — where influencer platforms see nothing at all.

Where Relio reaches — and how.

Four platforms, read by Relio itself. The list is short on purpose: a platform is here only when the evidence comes from the platform.

Automatic

Relio reads the platform itself: finds the placement, matches it, snapshots it, re-checks it. No creator action needed.

PlatformVerificationWhat Relio readsAfter verification
TelegramAutomaticChannel posts: full text, links, captions. Public channels read directly; an admin bot covers private ones.Re-checked at +24h and +7d. Edits caught by text hash; a deletion needs two confirmations.
YouTubeAutomaticVideos and Shorts via the official API: title, description, links.Re-checked at +24h and +7d. Edits caught by text hash; a deletion needs two confirmations.
TwitchAutomaticPast broadcasts and clips: titles, category, description. Clips are the durable record — Twitch expires VODs in 7–60 days.Snapshotted the day it appears, so the evidence outlives the VOD that expires.
KKickAutomaticStreams and clips: titles and category — the broadcast history no other monitoring tool reads.Re-checked at +24h and +7d. A deletion needs two confirmations.

Relio verifies what can be proven mechanically: text, titles, descriptions, links, codes, timestamps, existence. Nothing said inside a video or stream is machine-verified — which is why obligations are structured around checkable artifacts: the code in the description, the link in the post, the clip with the title. And when a check cannot run, the placement shows as unverified — which never converts into a violation on its own.

What counts as proof.

The hierarchy is strict — and it is the reason a green badge means something.

Hard evidence — can verify on its own

promo codeexact match in the text0.97
affiliate linkfound among the links0.93

These two can't appear by accident. That is why they are the only evidence that passes a placement automatically.

Soft signals — never enough alone

brand mentionkeywordhashtaglink pattern

They raise confidence, but on their own they always route to a person.

The AI is advisory. For grey cases a model reads the post and writes its reasoning. It can send a placement to review. It cannot verify one — ever.

Verified

Hard evidence present, score above a strict threshold. Snapshot filed.

Review

Your queue. The evidence is laid out — creator, post, what matched and what didn't — and a person decides.

“Unverified” never means “violated.”

  • A source that is blocked or down produces unverified — never “not compliant.”
  • A shortfall in a week with no healthy data settles as unverifiable — never as failed.
  • A breach is a verdict people make. Relio prepares the file; your operator signs the decision.

This is enforced in the pipeline, not promised in a policy.

The post is gone. The proof isn't.

Publish, get counted, delete quietly. Relio keeps checking after the placement is verified — and the record is append-only, so it cannot be edited away.

On the platform

3 Jul, 19:04

“New editor walkthrough is up — code MAKERS20 takes 20% off the annual plan.”

In Relio

Verifiedsnapshot #a91f4c
  1. Verified — promo code and affiliate link found. Snapshot filed.3 Jul, 19:04
  2. Re-check — post not found. Suspected, not concluded.+24h
  3. Second check — still missing. Deletion confirmed.+7d
  4. Verification invalidated · sent to your review queue.

Evidence is append-only — the record cannot be edited, by anyone.

Changed text re-runs the match — silent edits surface.

One bad response never costs a creator a delivered post — deletion needs two confirmations.

A morning, not a project.

Verified this week38
Needs review4
Unverified2
northline“editor walkthrough — code MAKERS20…”87% match
atlasdeskstream title missing the codeUnverified
Product UI — example data.

Your side

Checks run daily on schedule. What the system can prove, it settles. What it can't, it lays out for you — a handful of posts with the evidence attached, not a hundred open tabs.

Their side

Creators sign in with a magic link — no password, no app to install. They paste the URL of what they published; where the platform is reachable, it verifies on the spot.

Who runs on it.

Brokers and prop firms

Funded-account promos where the paid mention must actually appear — past the point where click tracking stops.

Crypto projects

Token and exchange placements across channels no listening tool indexes.

Agencies

Proving delivery to the client — per creator, per week, with the record to back it.

Built for rosters of 10 to 150 creators — past the point where a spreadsheet survives, below the point where an enterprise suite makes sense.

See it on one of your own agreements.

Bring one live creator deal. We set it up together and run the first verification pass on your real placements — you watch the evidence arrive.