Skip to main content
Surface: https://api.aegis-kyt.com/v2/*
The V2 API is the account-based counterpart to x402. Where x402 is per-call USDC for AI agents that don’t want accounts, V2 is the traditional API model for businesses: an API key, a prepaid credit balance, and the same per-call prices as x402 (1 credit = 1 USDT of top-up). Both surfaces run the SAME Aegis 4-tier engine and return the same single Aegis verdict. Pick whichever fits your usage model.

​
Pricing vs x402 — same logic, different channels

Some V2 endpoints return data that x402 also sells. The compute is identical (same SQL, same Python aggregator) — what differs is the settlement rail: Most direct overlap: Practical consequence: if you’re a partner wallet putting a screen behind every “send to address” prompt for your users — use the V2 API. x402 is for callers who don’t have an account relationship with us.

​
Quickstart

​
Endpoints

Billing is per your plan / commercial agreement. See the per-endpoint pages for full request/response shapes.

​
Authentication

  • One active key per user.
  • Plaintext shown once at creation. Server stores SHA-256 only.
  • Revoke / rotate via /account?tab=api in your kabinet.
  • Missing or invalid key → HTTP 401.

​
Billing

Every call is priced in credits and debited from your account balance. 1 credit = 1 unit of your balance = 1 USDT of top-up, so the numbers match x402’s USDC prices: Top up in USDT on TRON at app.aegis-kyt.com/topup: 10 USDT → 11 credits, 50 → 60, 100 → 125 (the bonus grows with the amount). Credits never expire.
  • Polling a result is free; repeated polls of the same check are not charged again.
  • Unsupported networks are rejected before any charge.
  • Insufficient balance → HTTP 402 code: insufficient_funds. The 402 body carries balance_credits / requested_credits next to balance_usd / requested_usd (same values); its human-readable message still prints $ amounts, so parse the numeric fields, not the message.
  • Optional monthly cap exceeded → HTTP 402 code: monthly_cap_exceeded.
  • Balance and spend: GET /v2/balance or GET /v2/me/usage; live prices: GET /v2/networks → prices_credits (same numbers as prices_usd).
  • Every billing block carries credits_charged, credits_balance, credits_monthly_spent, credits_monthly_cap and unit: "credits" alongside the unchanged *_usd fields — see the changelog. No field was renamed or removed.

​
Refunds

​
Idempotency-Key

Send Idempotency-Key: <≤64 chars> header to make retries safe:
  • Same key + same body within 24h → cached response, no charge
  • Same key + DIFFERENT body → HTTP 409 idempotency_conflict
Use any high-entropy token (UUID v4 recommended).