solSafe

2026年8月3日1 次浏览来源:Dev.to阅读原文

I sell Solana token facts for two cents a call, and refuse to give an opinion While building this I ranked a token's trading pairs by pool depth, which seemed obviously correct.

It picked JUP's biggest pool — quoted in an obscure token — and reported a price of $943 against a real price of about $0.19.

A 5000x error that would have silently poisoned everything downstream.

Depth doesn't make a derived price trustworthy; what it's quoted against does.

That bug is why the service now always prefers SOL/stablecoin-quoted pairs, and says so explicitly when the best available pair is still exotic.

That's the whole design philosophy. solsafe returns measured values — mint and freeze authority, holder concentration, pool depth and age, pump.fun origin — and never a score, signal, or recommendation.

You can reproduce every field against your own RPC.

An opinion can be wrong in ways a null mint authority cannot.

The other unusual part is billing.

It's paid per request over x402: call it, get a 402 with machine-readable payment instructions, pay in USDC on Base, retry, get JSON.

No API key, no signup, no dashboard — which is the point, because the intended caller is an autonomous agent that can't complete a signup flow. $0.02 for the raw facts, $0.15 for a written brief explaining them.

Things I'd rather say up front than have you discover: holder concentration is permanently unavailable for the most widely held tokens, because Solana's RPC refuses that query outright.

A failed or partial call isn't charged.

And demand for this is entirely unproven — agent-native payments are early, and I might be wrong that anyone wants it.

Code: github.com/newbieBuilderr/solsafe

分享
Baike.dev

baike.dev helps you discover great languages, frameworks, databases, DevOps and cloud-native tools.

Quick links

About

Contribute

Found a great developer tool? Share it with the community.

Submit a tool
© 2026 baike.dev Developer EncyclopediaUpdated daily · Discover great developer tools