Ban usersacross accounts.
Plug Claymore into your game or platform. When someone you banned shows up on a fresh account, with the same behavior and writing style, get a flag and take a look.
Nova ArenaA made-up game
Made-up dataToday’s queue
Last run tonight: 102 pairs scored, 34 of 36 active accounts had enough text to score. 4 flags cleared the floor of 0.86.
Show the top 25 by score
A quiet night gives a shorter queue than you asked for; that is intended.
Recommended: 4
Cold startMedian count above the floor over the last run.
| # | Account | Writes like | Score | Above | Signals | Open |
|---|---|---|---|---|---|---|
| 1 | nightglass_7 | vanta_fox | 0.940 | 99.0% | Created after ban2 shared friends | |
| 2 | r0cket_raccoonRocket Raccoon | RocketRaccoon | 0.912 | 97.8% | Created after banSimilar name | |
| 3 | pixel_otter2 | tidepool_22 | 0.889 | 96.1% | 1 shared friendPlayed at the same time | |
| 4 | moss_and_mint | kettledrum | 0.871 | 94.6% | 1 shared friend |
Forget the username. Watch how they act and write.
Go ahead: swap the name, the email, the device. Now try acting and typing like somebody else.
Plug it into what you already run.
Unity
Forward chat from your game server. Get scores back in the moderation flow you already have.
Engine
Unreal Engine
Send chat events from your dedicated server. Leave the client alone.
Engine
Godot
Score messages from your multiplayer backend. Set it up in a few lines.
Engine
Roblox
Score messages straight from your experience's server scripts.
Platform
Discord
Bring your game's Discord server along. Use the same fingerprints there.
Community
Webhooks
Post chat events over HTTPS from any stack. Read the scores in the response.
Any backend
REST API
Skip all of this and call it yourself.
Direct
Make three calls. Get your first match.
- 01
Store a confirmed case
When your team confirms a report, send in that account's messages. Pick any subject ID you like.
POST /enroll
- 02
Score new accounts
Send messages from new accounts. Get back the closest stored cases, each with a score.
POST /retrieve
- 03
Let a person decide
Hand anything above your threshold to a reviewer. Remove a case any time with DELETE /subjects/{id}.
Your review queue
# Score a new account's message against your stored subjects
curl https://api.useclaymore.com/retrieve \
-H "X-Api-Key: $CLAYMORE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"text": "ur honestly so good at this.. like for real tho",
"k": 5,
"threshold": 0.75
}'Let it raise the flag.You make the call.
Hand Claymore the watching, night after night. Keep the judgment: your reviewers, your policies, your appeals.
01Use it to look closer
Use Claymore to notice when a new account behaves and writes like one your team has already confirmed. Then have a person take a closer look.
02Read a match as similar, not the same
Take a match to mean two accounts behave and write alike. Don’t take it as proof of who someone is, or that they did anything wrong.
03Review in context
Send every potential match to a trained reviewer. Have them read the surrounding conversation, the account history, and your policies before doing anything.
04Expect mistakes. Allow appeals.
Remember that different people can act and write alike, so plan for false positives. Keep a review step, write decisions down, and give players a clear way to appeal.
05Set your own rules
Decide retention, access, consent and privacy for your own deployment, within the law that applies to you. Delete stored cases through the API whenever you need to, and allow for backups lingering through a limited recovery window.
Tell us about your game or platform.
Fill in a few details and get an API key back.
Want to poke around first? Read the docs