---
title: "Batch buyer-quality scoring (up to 50 mints)"
method: POST
path: "/tokens/batch/buyer-quality"
tags: ["Tokens"]
---

# Batch buyer-quality scoring (up to 50 mints)

`POST /tokens/batch/buyer-quality`

## Request

- Base URL: `https://madeonsol.com/api/v1`
- URL: `https://madeonsol.com/api/v1/tokens/batch/buyer-quality`
- Auth: HTTP bearer

Same per-mint shape as `GET /tokens/{mint}/buyer-quality`. Shares the LRU cache with the single-mint endpoint — already-warm mints return at ~zero cost. Response includes `cache_hits` counter.

**Coverage** (additive): each item carries `in_scope` (boolean|null) derived from whether that mint had early-buyer rows in our capture — `false` may simply mean 'no early-buyer rows', not proof the token never traded (the batch path does not run the per-mint probe; use the single-mint endpoint for a probed verdict). A top-level `coverage` object carries the shared `history_start` + `scope` markers once.

## Request body

- object
  - `mints` union, required: Up to 50 Solana token mints — a comma-separated string or a JSON array
    - string
    - string[]

## Response `200`

OK. Response contains `tokens[]`, `count`, and `cache_hits`.

- object
  - `tokens` object[]
    - `mint` string
    - `score` number: 0-100 composite buyer-quality score
    - `confidence` 'insufficient_data' | 'low' | 'medium' | 'high': Confidence in the PREDICTIVE inputs: counts only buyers whose win rate fed the score (≥3 tokens of history, not bot-flagged, not zero-cost-dump dominated). insufficient_data = none did — the score is the neutral-50 default plus penalties. 1 → low, 5+ → medium, 11+ → high.
    - `signal` 'positive' | 'neutral' | 'negative'
    - `breakdown` object
      - `alpha_wallet_count` integer
      - `kol_count` integer
      - `bundle_buyer_count` integer
      - `avg_historical_win_rate` number, nullable: null when no buyer's win rate qualified (confidence insufficient_data)
      - `bot_dominated` boolean
      - `wallets_with_history` integer: Buyers with ≥3 tokens of history (cohort identification — not predictive)
      - `qualified_win_rate_wallets` integer: Buyers whose win rate fed the score — the basis of confidence
      - `dump_cluster_count` integer: First-20 buyers on the rolling dump-cluster list (wallets whose 5+ recent first-20 appearances are exclusively on tokens that peaked <15 min after deploy; trailing 42d, refreshed daily). Out-of-sample: 3+ such wallets predicted a sub-15-min peak 94% of the time vs 61% base. Informational — does not move the score.
      - `recycled_early_buyer_count` integer: First-20 buyers with 5+ recent first-20 cohort appearances of any kind. The count alone predicts nothing; a heavily recycled cohort with dump_cluster_count 0 historically leans runner.
    - `cached_at` string, date-time
    - `coverage` TradeCoverage: Coverage disclosure for endpoints backed by our persisted trade capture (`token_trades` / early-buyer data). Capture starts 2026-04-12 and persistence is gated to the launchpad pipeline (pump.fun, LaunchLab/bonk, bags) — it is NOT a full Solana trade history. Three separate answers (2026-09-21): `data_observed`/`in_scope` = at least one persisted row (presence, not completeness — a brand-new in-scope mint with no trades yet also reads false), `eligibility` = whether the CURRENT gate admits the subject, `completeness` = always `not_verified`. When no rows exist, zero/empty values mean 'not captured' (see eligibility for why), never 'no activity'.
      - `history_start` integer: Epoch seconds of the first persisted trade (2026-04-12).
      - `scope` string
      - `in_scope` boolean, nullable: Kept for compatibility — same value as data_observed: true = we hold ≥1 persisted trade for this subject · false = none persisted (see eligibility for why — a brand-new in-scope mint also reads false) · null = probe unavailable
      - `data_observed` boolean, nullable
      - `eligibility` 'eligible' | 'lapsed' | 'excluded' | 'unknown' | 'admitted_previously' | 'not_applicable' | 'null', nullable: Resolved against the EFFECTIVE production capture settings (refreshed every few minutes; if they cannot be confirmed the answer narrows, never widens). eligible = admitted by the current gate · lapsed = launched via our pipeline, capture window closed under the current settings · excluded = blacklisted · unknown = no evidence the gate admits it (most likely outside the launchpad pipeline; basis capture_state_unavailable = settings could not be confirmed, no claim either way) · admitted_previously = persisted rows prove past admission, current status not established · not_applicable = wallet subjects · null = lookup failed
      - `eligibility_basis` string, nullable: Evidence behind eligibility (e.g. unresolved_launch, recently_bonded, revived_curve, pipeline_known, launchlab_pool, bags_vanity_mint, launchpad_proven, resolved_launch, bonded_over_7d, revival_expired, blacklisted, persisted_rows, capture_state_unavailable, lookup_failed)
      - `completeness` 'not_verified'
      - `size_floor` object: Persistence size floor of the same write path (added 2026-09-30). Buys under 0.05 SOL (under $3.50 when paid in USDC/USDT) are not stored; sells that receive SOL are kept at any size. Live streams, prices and candles are not subject to it.
        - `min_sol` number
        - `min_stable_usd` number
        - `applies_to` string
      - `note` string: How to read the values (always present since 2026-09-21: eligibility-specific when no rows exist, a completeness caveat when they do).
    - `note` string: Present when the mint had no early-buyer rows to score, e.g. "Insufficient buyer data"
    - `in_scope` boolean, nullable: Whether this mint had early-buyer rows in our capture. false may simply mean no early-buyer rows, not proof the token never traded — the batch path skips the per-mint probe GET /tokens/{mint}/buyer-quality runs.
  - `count` integer
  - `cache_hits` integer
  - `coverage` object
    - `history_start` string
    - `scope` string
    - `note` string

## Other responses

- `400`: Invalid body or mint
- `401`: Missing or invalid API key, or an expired free-tier key. Authentication-stage error: no `X-RateLimit-*` headers, no `_rid`.
- `403`: Forbidden. One of: the key's tier is below this endpoint's or parameter's gate (`tier_required` with an `upgrade` block); the public demo key used outside its allow-list (`demo_key_endpoint_not_allowed`); an invalid or revoked key; an origin-restricted key called from a disallowed origin (`code` `origin_not_allowed` / `origin_required`). `X-RateLimit-*` headers are present only on `tier_required`.
- `429`: Too many requests. Every 429 carries `Retry-After`. A quota 429 (`rate_limit_exceeded`, with `X-RateLimit-*`), a heavy-query concurrency 429 (`error_kind` `concurrency`/`capacity`), or the per-IP authentication-failure block (30 failed auths/min; plain `error` + `retry_after_seconds`, no `X-RateLimit-*`).
- `500`: Unexpected server error from the route (`Internal server error`, with `_rid`). Safe to retry with backoff. A failed API-key lookup is a 503 `auth_backend_unavailable`, never a 500.
- `503`: The API-key or subscription lookup could not be answered (authentication stage). Retryable and not your fault: it is never counted as a failed authentication. Honour `Retry-After`; no `X-RateLimit-*`, no `_rid`.

---

[API](https://skmtc.dev/madeonsol/apis/madeonsol-api.md) · [All operations](https://skmtc.dev/madeonsol/apis/madeonsol-api/llms.txt) · [OpenAPI document](https://skmtc.dev/madeonsol/apis/madeonsol-api/revisions/96ce84657f55?raw)