Age and identity checks for communities and creators

Check age at the door, verify the people you pay, and keep banned users from coming back with a new account.

Who it's for

Paid communities and bots
Groups, channels and servers on Telegram, Discord and similar apps. Your bot sends a verification link and lets the user in when the result arrives.
Creator platforms
Check that fans are adults before they see age-restricted content, and verify creators before you pay them.

Running a marketplace? See Marketplaces.

Keep banned users out

ProofAge can remember faces and devices, so a ban sticks. It works with face, ID and KYC checks and is included in the price. How Block repeat accounts works.

Block by face

Ban someone once, and a later verification with the same face is caught, whatever email, phone number or document they use. By default your blocklist covers only your own account.

Block by device

Block the device a banned user verified from, so a new account from that device is caught too.

Find duplicates

See when the same person verifies for several accounts, without waiting for a ban: trial abuse, ban evasion, sock puppets.

Verify your own creators

Run Identity verification (KYC) before you pay a creator or mark them as verified, and get the identity data from their document.

Which check fits

  • Keep a group, server or content 18+

    Facial age estimation

    A selfie with liveness. If the face is inconclusive, it falls back to an ID document at no extra cost. From $0.05.

  • Check age against a document

    Age verification by ID

    Over or under your age threshold, plus first name, last name and date of birth. $0.30.

  • Know who your creators are before payouts

    Identity verification (KYC)

    All the data from the document and the document type. $0.30.

Each of these checks can run with Block repeat accounts, so bans stick and duplicates show up. Compare all checks; the monthly plan, billing rules and programs are on the pricing page.

How it works

  1. Step 1

    Create a verification

    Your backend or bot calls the API and gets a link for the user.

  2. Step 2

    The user completes it

    In the hosted widget, with the camera of their phone or computer.

  3. Step 3

    The result arrives

    By signed webhook. Check the signature, then grant the role, unlock the content or approve the payout.

We help you integrate: ready SDKs, an MCP server and an integration prompt for AI coding agents, and direct help from the developers who built it. SDKs: Laravel/PHP, Node.js, Python.

Questions from communities and creators

Can a banned user come back with a new account?

Not if you use the blocklists. When you ban someone, you can put their face and device on your blocklist. A later verification with the same face or from the same device is caught, even with a new email, phone number or document.

How do you find one person behind several accounts?

Duplicate detection compares each verification with the face templates from earlier verifications in your account, kept for 12 months. If the same person already verified for another account, the result tells you.

Does it work with a Telegram or Discord bot?

Yes. Your bot calls the API to create a verification and sends the user the link. The user completes it in the hosted widget, and the result reaches your backend by signed webhook, so the bot can grant access.

Which check should we use for an 18+ group or channel?

Facial age estimation. Most adults pass with a selfie, and if the face is inconclusive it falls back to an ID document at no extra cost.

Do the blocklists cost extra?

No. The face blocklist, the device blocklist and duplicate detection are included in the price of every face, ID and KYC check.

Will you do the integration for us?

We help you integrate: ready SDKs, an MCP server and an integration prompt for AI coding agents, and direct help from the developers who built it. The SDKs cover Laravel/PHP, Node.js and Python.

Try it on your own users

500 free verifications, no time limit, no card. Questions first? Talk to the developers who built it.