Guardian for Tournament Organizers

Guardian answers one question for competition: can this player be trusted to play? Roster clearance is that question asked about everybody at once, held open from the moment entries close until the event starts.

The problem it solves

Most organizers verify entrants once, at signup, and then hope. The gap between signup and kickoff is where the trouble is. A player who was clean when they registered can pick up a ban, change machines, or be caught by somebody else's tournament in the weeks between — and you find out when a rival team complains in your Discord, after the final.

Clearance closes that gap. You submit your line-up once, and it stays evaluated against current standing for as long as the event is open.

What you get

• A verdict for every seat: clear, review, blocked or unknown.
• The reasons behind each verdict, so a decision can be explained to the player it affects.
• A roll-up per roster, so you can see at a glance whether an event is ready.
• Alerts when a player's standing moves, rather than at the next time you happen to look.

What it is not

Clearance is not a live anti-cheat running during your match. It is a statement about a player's standing and their most recent verified scan. If you need proof that a specific machine was clean at the moment a specific match started, that is a match attestation, and it is a different tool — see Attestations vs. clearance.

Getting started

1. Talk to us about your competition; we issue a partner key with a sandbox environment.
2. Submit a roster with your entrants' handles.
3. Read the verdicts, and decide your own eligibility rules from them.
4. Add a webhook so you hear about changes before match day.

The endpoint reference, with request and response examples, is at /guardian/docs.