Dossier

← New launches

Pons launch

$VETO Veto Protocol

Launched by 0xab90…47ee Graduated

0x0d099caf7e87626c8327f01471a142d244900f7f

VerifiedVerified 28 min after launch
Market cap
—
Change
—
24h volume
—
24h buys / sells
—
Price
—
Curve
—
Real holders
—
Agent balance
—

Market numbers come from Orbio and cover Orbio agents only.

Is this the project's token?

The official account @vetoprotocol posted this contract.

The project's own X account or website lists this exact contract.

The project

Veto Protocol is a programmable security layer that evaluates and enforces what AI agents may do across apps, data, and wallets.

Summarised from the site and posts it points at; the quote behind it was checked against the page.

Building control infrastructure for the agentic era. Defining what autonomous systems can access, execute and delegate.

The token description, written by whoever launched it.

@vetoprotocol · 69 followers · joined Sep 2026 · 8 posts in 4 weeks

Building control infrastructure for the agentic era. Defining what autonomous systems can access, execute and delegate.

Score

Live

40/100

A working product with an accountable team or active code.

Product18/30
Build0/20
Team8/20
Work4/20
Integrity10/10

Trader’s card

Original or copy

  • 7th token named $VETO. The first, $VETO, launched 3 days earlier. The project's own channels confirm this one.

In launch order, coloured by verdict. This one is ringed.

Creator

  • This wallet launched nothing else within a week of this one
  • New wallet: first active 27 Sep 2026
  • Bought 27.78M at launch and has sold 0% of it

Launch

  • Nobody bought in the launch block itself
  • 28 wallets took 27.6% of the supply in the first 10 seconds (6 of them bots that buy most launches). 9 had sold or moved it within 30 minutes

Holders

  • Top 10 holders own 18%
  • Real holders: 329 after 30 min

From the chain alone: holder counts are real end buyers, not routers or bots, and bots are wallets that buy 10 or more launches a day.

Who it points at

The accounts and sites in the token's own metadata, and whether each one claims this token. Metadata is written by the launcher, so only the claim counts.

KindLinkClaims it?
Websitevetoprotocol.live named names the ticker or project, not this contract
X accountx.com/vetoprotocol bound claims this token: it posted or lists this contract

Evidence log

13 checks, each with what it found and when

A line counts only if its source claims the token (the weight), and it fades as it ages.

Product 18 of 30

Site responds 4.8 (12 × 0.4) HTTP 200
Site has real content 2.4 (6 × 0.4) 288 words
A working page beyond the homepage 0 (0 × 0.4)
Site changed in the last 14 days 0 (0 × 0.4)

Team 8 of 20

X account claims the token 8 @vetoprotocol, 69 followers
X account age at launch 0 8 days old
Posts most weeks 0 active 1 of the last 4 weeks, 8 posts
Creator wallet has history 0 first seen 2026-09-27

Work 4 of 20

Verified product output (7 days) in its posts 4
  • 2026-09-30 Published a walkthrough showing an AI agent requesting Google Drive contents through Veto's tooling along with the connected-apps management dashboard A closer look at Veto protocol. This walkthrough shows an AI agent requesting Google Drive contents through Veto’s tooling, alongside the dashboard for… post
Verified product output (7 days) on its site 0 (0 × 0.4) none in the last 7 days

Integrity 10 of 10

Holders not concentrated 4 top 10 hold 18% of supply, 224 holders
Creator didn't dump 3
Creator fees not redirected 3

Raw data for this file: 0x0d099caf….json