---
title: "Skill curve for one deployer"
method: GET
path: "/deployer-hunter/{wallet}/trajectory"
tags: ["Deployer Hunter"]
---

# Skill curve for one deployer

`GET /deployer-hunter/{wallet}/trajectory`

## Request

- Base URL: `https://madeonsol.com/api/v1`
- URL: `https://madeonsol.com/api/v1/deployer-hunter/{wallet}/trajectory`
- Auth: HTTP bearer

Aggregated MC-at-bond and time-to-bond trends over the deployer's launch history. Surfaces whether they're improving or fading.

## Path parameters

- `wallet` string, required

## Query parameters

- `include` 'daily_snapshots'

## Response `200`

OK

- object
  - `coverage` LaunchCoverage: Dataset-scope disclosure injected on every 200 from the launch-pipeline feeds (`/deployer-hunter/*`, `/sniper/*`, `/alpha/*`, `/tokens/almost-bonded`, `/tokens/batch/risk`, `/wallet/batch/classify`) unless the route already carries a more precise per-subject `coverage`. Static: these datasets are built from launchpad ingest (in practice ~99% pump.fun), so an absent wallet/token, an empty profile or a `false` reputation flag means 'not observed by this pipeline', never 'clean' or 'no activity'.
    - `scope` string
    - `note` string: How to read absences and zeros in this response.
  - `is_deployer` boolean, nullable: Only present (false) for untracked wallets; omitted otherwise
  - `wallet` string: Echo of the requested wallet — only on the is_deployer:false body
  - `deployer` object, nullable: null when the wallet isn't a tracked deployer
    - `wallet_address` string
    - `total_tokens_deployed` integer
    - `total_bonded` integer
    - `bonding_rate` number, nullable
    - `recent_bond_rate` number, nullable
    - `tier` 'elite' | 'good' | 'moderate' | 'rising' | 'cold', nullable
  - `trajectory` object, nullable: null when the wallet isn't a tracked deployer
    - `current_streak` object
      - `type` 'bond' | 'fail' | 'none'
      - `count` integer
    - `longest_bond_streak` integer
    - `longest_fail_streak` integer
    - `rolling_bond_rates` object[]: Rolling 10-token bond-rate windows
      - `window_end` integer
      - `bond_rate` number
    - `trend` 'improving' | 'declining' | 'stable'
    - `avg_days_between_deploys` number, nullable
    - `avg_recovery_tokens` number, nullable: Avg tokens between a fail streak and the next bond
    - `best_stretch` object, nullable
      - `start_index` integer
      - `end_index` integer
      - `bond_rate` number
    - `worst_stretch` object, nullable
      - `start_index` integer
      - `end_index` integer
      - `bond_rate` number
    - `total_tokens_analyzed` integer
  - `daily_snapshots` object[]: Only present when include=daily_snapshots
    - `snapshot_date` string, date
    - `tier` string, nullable
    - `total_tokens_deployed` integer
    - `total_bonded` integer
    - `bonding_rate` number, nullable
    - `recent_bond_rate` number, nullable
    - `avg_peak_mc` number, nullable
    - `best_token_peak_mc` number, nullable

## Other responses

- `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)