OFFICIAL VERIFICATION PROTOCOL

The Verified badge.Earned, not bought.

Any operator can launch a portal in 60 seconds. The Verified badge signals that a portal has passed a manual review — admin identity, token legitimacy, community history. It's the trust layer that separates legitimate token communities from imitators.

REQUEST VERIFICATION ▸
✓
● AGENT K VERIFIED
PORTAL
REVIEW PASSED
ELIGIBILITY ● ALL FOUR REQUIRED

What we check.

These are the minimum requirements. Meeting them doesn't guarantee the badge — review is manual and we retain discretion to reject.

01
ADMIN IDENTITY
Telegram account age > 90 days. Must link to the token project's public accounts (Twitter/X, official Discord/Telegram, website) and control at least one of them.
02
TOKEN LEGITIMACY
Contract address reviewed for: ownership renounced or time-locked, liquidity depth sufficient for claimed threshold, no obvious honeypot / blacklist / fee-swap functions in the contract.
03
COMMUNITY STANDING
Portal must be on PRO or ELITE tier. Minimum 25 active members. At least 14 days of clean activity history with zero impersonator strikes or anti-raid lockdowns.
04
AGENT P INTEGRATION
Agent P must be active in the same Telegram group with captcha + impersonator detection enabled. Defensive protocol is mandatory for the Verified tier.
WHAT THE BADGE UNLOCKS

Pending portal vs. Verified portal.

Side-by-side of how a portal appears across the network before and after verification.

● PENDING PORTAL

  • Listed in directory, but sorted below verified portals
  • No verified badge in search results
  • Not eligible for Featured rotation on the homepage
  • Admin flagged as "unverified" in Mini App
  • No automatic placement in token-specific recommendation feed
  • Members see "Verification pending" on portal page

● VERIFIED PORTAL

  • Top-sorted in directory for its token
  • Gold checkmark badge visible everywhere
  • Eligible for Featured rotation on agentk.pro homepage
  • Admin shows as "Verified operator" in Mini App
  • Surfaced to new wallets holding the token via bot onboarding
  • Credibility signal for new members considering joining
APPLICATION PROCESS

From request to badge — typically 3–7 days.

STEP 01
Submit request via Mini App
Open Agent K → your portal → Admin → Request Verification. You'll be asked for your project's public links, admin proof, and token contract details.
STEP 02
Automated pre-checks
Tier check, member count, activity history, and contract static analysis run immediately. Failures here are reported back in under a minute so you can fix and resubmit.
STEP 03
Manual review
A member of the verification team posts to a designated review group. Admin identity confirmation usually requires a public tweet or Telegram pin from the project's official account.
STEP 04
Decision + badge
Approved: badge applied instantly across all surfaces. Rejected: you get a reason and a 14-day cool-down before re-applying. No fees either way — verification is free for eligible portals.

Think your portal qualifies?

Open Agent K → your portal admin panel → Request Verification. Applications reviewed in order.

REQUEST VERIFICATION ▸