AntiVampAntiVamp

Partner console

Integrate AntiVamp

Create a sandbox key, validate launches against seeded scenarios, receive signed webhooks, and request production access when you're ready.

Developer docs

Create a sandbox key

Instant, self-serve, free. Sandbox keys validate against seeded scenarios and never touch production enforcement.

Already have a key?

Paste it to open the console — usage, request logs, webhooks, and delivery replay.

How the integration works

  1. 1

    Create a sandbox key

    Self-serve, instant, free — from the console below. Sandbox keys validate against seeded scenarios (reserved, protected, expired, blocked, guardian-cleared) and never touch production enforcement.

  2. 2

    Validate before every launch

    Call the validate endpoint with the exact chain, name, ticker, and launcher wallet a creator is about to deploy with. Decisions are HMAC-signed with your key's secret and expire after 5 minutes.

  3. 3

    Respect the decision

    'allow' → proceed. 'allow_authorized_only' → proceed only for the authorized wallet. 'block' → reject and surface the reason. 'recheck_required' → data was unavailable; fail closed and retry.

  4. 4

    Report launches and milestones

    Report launches, bonding, and verified milestones so protection windows extend across the network — longest lock always wins, and locks never shorten. Subscribe to signed webhooks for state changes.

Request
POST /api/v1/launches/validate
Authorization: Bearer av_sbx_your_key
Content-Type: application/json
Idempotency-Key: launch-attempt-8f2c

{
  "chain": "base",
  "launchpad": "your-launchpad",
  "name": "GREENROBIN",
  "ticker": "ROBIN",
  "launcher": "0x7a1b2c3d4e5f6789012345678901234567890abc",
  "nonce": "launch-attempt-8f2c"
}
200 response
{
  "identityKey": "GREENROBIN::ROBIN",
  "normalizedName": "GREENROBIN",
  "normalizedTicker": "ROBIN",
  "status": "authorized",
  "decision": "allow",
  "authorizedLauncher": "0x7a1b…0abc",
  "protectedUntil": "2026-09-14T18:00:00.000Z",
  "reason": "reserved_launch_bonded",
  "issuedAt": "2026-07-16T08:00:00.000Z",
  "expiresAt": "2026-07-16T08:05:00.000Z",
  "nonce": "launch-attempt-8f2c",
  "responseVersion": "2026-07-16",
  "environment": "sandbox",
  "signature": "hmac-sha256-hex…"
}

Ready to integrate?

Try the validate endpoint from your own backend, then reach out for partner access.

Request partner access