Launch Odds
by AgentFeed in Onchain & crypto
Launch odds: the share of a launchpad's followed pools whose liquidity was removed, collapsed, went inactive or stayed active at 1, 7 and 30 days, with n. Use when you need to answer: What share of launches on this Solana launchpad survive 1, 7 and 30 days? Narrow it to a t0 liquidity band, or pass a mint for its pools, t0 snapshot, authorities and outcome labels. Only pools past our ledger's…
https://x402.ochinimus.app/api/launch-odds- Price
- $0.01
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 44 h ago, next in 29 h
Reliability
Latest check failed 44 h ago: Expected HTTP 402, got 410
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://x402.ochinimus.app/api/launch-odds
Each call costs $0.01 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://x402.ochinimus.app/api/launch-odds?launchpad=pump-funParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
launchpad | string | No | launchpad or DEX as the ledger names it, e.g. pump-fun, pumpswap, meteora-dbc, raydium-launchlab, bags-fm; an unknown name lists them |
mint | string | No | a Solana mint instead of a launchpad: that mint's pools, t0 snapshot and outcome labels |
t0_liq_usd | number | No | liquidity at discovery in USD: narrows the launchpad odds to that band (0-5k, 5-10k, 10-25k, 25-50k, 50-100k, 100-250k, 250k+) |
Example response
The provider's example. We can't check it without paying.
Example response, 58 lines
{
"data": {
"aggregated_at": "2026-10-12T05:27:51.641Z",
"as_of": "2026-10-12T05:21:08.000Z",
"chain": "solana",
"cohort": "Only pools that crossed the ledger's traction threshold are followed: liquidity of 5000 USD or more or 24h volume of 1000 USD or more at dis…",
"horizons": [
{
"counts": {
"active": 99939,
"inactive": 1658,
"liquidity_collapsed": 2933,
"lp_removed": 10110
},
"excluded": {
"unknown": 18203,
"unresolvable": 0
},
"horizon_days": 1,
"n_decided": 114640,
"share": {
"active": 0.8718,
"inactive": 0.0145,
"liquidity_collapsed": 0.0256,
"lp_removed": 0.0882
}
},
{
"counts": {
"active": 111,
"inactive": 109950,
"liquidity_collapsed": 2712,
"lp_removed": 9678
},
"excluded": {
"unknown": 419,
"unresolvable": 0
},
"horizon_days": 7,
"n_decided": 122451,
"share": {
"active": 0.0009,
"inactive": 0.8979,
"liquidity_collapsed": 0.0221,
"lp_removed": 0.079
}
}
],
"labels": "lp_removed: liquidity fell 90% or more from its in-window peak and is under $1,000, or the pool is gone. liquidity_collapsed: fell 70% or mo…",
"launchpad": "pump-fun",
"mode": "launchpad",
"pools_followed": 134708,
"source": "LaunchLedger (our own Solana launch-to-outcome ledger), read-only",
"t0_liquidity_band": null
},
"paid": true,
"tool": "get_launch_odds"
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://x402.ochinimus.app/api/launch-odds?launchpad=pump-fun'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://x402.ochinimus.app/api/launch-odds?launchpad=pump-fun' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fx402.ochinimus.app%2Fapi%2Flaunch-odds
const res = await pay("https://x402.ochinimus.app/api/launch-odds?launchpad=pump-fun");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://x402.ochinimus.app/api/launch-odds?launchpad=pump-fun")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 44 h ago | Expected HTTP 402, got 410 | 410 | 262 ms | - |
| 2 days ago | Expected HTTP 402, got 410 | 410 | 195 ms | - |
| 2 days ago | Expected HTTP 402, got 410 | 410 | 250 ms | - |
| 2 days ago | Expected HTTP 402, got 410 | 410 | 156 ms | - |
| 3 days ago | Expected HTTP 402, got 410 | 410 | 164 ms | - |
Show 10 older checks
| 3 days ago | Expected HTTP 402, got 410 | 410 | 235 ms | - |
| 3 days ago | Expected HTTP 402, got 410 | 410 | 122 ms | - |
| 3 days ago | Expected HTTP 402, got 410 | 410 | 57 ms | - |
| 3 days ago | Expected HTTP 402, got 410 | 410 | 258 ms | - |
| 4 days ago | Expected HTTP 402, got 410 | 410 | 175 ms | - |
| 4 days ago | Expected HTTP 402, got 410 | 410 | 254 ms | - |
| 4 days ago | Expected HTTP 402, got 410 | 410 | 233 ms | - |
| 4 days ago | Expected HTTP 402, got 410 | 410 | 291 ms | - |
| 4 days ago | Expected HTTP 402, got 410 | 410 | 157 ms | - |
| 4 days ago | Expected HTTP 402, got 410 | 410 | 201 ms | - |