Pool x402 REST usage
Yield pool safety: peg of every underlying asset, yield sustainability, emission dependence, exit depth
0.015 USDC per call
per call
poolproof.ru
poolproof.ru · 9 listed services · provider site
Launch x402 REST usage
Who launched this pump.fun token and what happened to their previous ones: launch count, graduation record, and whether the creator bought their own bonding curve
0.015 USDC per call
per call
Exit cost x402 REST usage
Real cost of exiting a Solana position AT YOUR SIZE — live route, not theoretical slippage
0.01 USDC per call
per call
Safety x402 REST usage
Is this Solana token safe to touch: mint and freeze authority status, top-holder concentration, Token-2022 transfer risks, and the deployer's full launch record from our own recording. Flags MINT_AUTHORITY_LIVE, FREEZE_A...
0.01 USDC per call
per call
Launches x402 REST usage
Live feed of pump.fun launches from the last 24h with creator context: who deployed each one, how many they launched before, whether they bought their own bonding curve. Poll with ?since= for only what is new. This histo...
0.01 USDC per call
per call
Deployer x402 REST usage
The full launch record of a Solana wallet from our own live recording: how many tokens it deployed, how many reached the exchange, its graduation rate against measured base rates, and whether it is a serial minter with n...
0.01 USDC per call
per call
Known x402 REST usage
Do we hold a research note on this asset, protocol, chain or role that no price feed or TVL number will tell you: dead redemption bridges, ticker collisions, ended points programmes, closed marketplaces, capital gates
0.02 USDC per call
per call
Stable x402 REST usage
Is this stablecoin's $1 peg a hard anchor or a soft peg: does its price historically return to $1 (a redemption/arbitrage anchor) or sit below it (the market pricing risk), and is it dislocated right now. Flags SOFT_PEG,...
0.01 USDC per call
per call
Chain x402 REST usage
Is this chain alive: TVL trend over 1y/6m/90d/30d
0.009 USDC per call
per call
Provider identity is derived from the domain or repository in the source record. If two vendors share a host, they appear together here — that is a limitation of the data, not a statement about ownership.