RiskDataAPI

JSON risk-scoring for Solana tokens. Built for AI agents & trading bots. MCP server, x402 support. First-funder cluster detection.

[RiskDataAPI @RiskDataApiSol]

**1/7**
🛡️ Introducing Risk-Data API by TNT House

One GET request tells your trading bot everything it needs to know before buying a Solana token — built for AI agents, not dashboards for humans.
**2/7**
Most Solana bots buy blind. They check price and volume, but miss the thing that actually rugs people: insider wallets quietly holding supply through connected addresses that look "distributed" on the surface.
**3/7**
Our killer feature — insider_clusters — finds wallets that share the same first-funder. An on-chain-provable signal, not a guess. If 5 "different" wallets were all funded by the same source, that's not organic distribution. That's one entity hiding.
**4/7**
Every response includes:
• Safety Score (0–100)
• Insider cluster detection
• Mint/freeze authority status
• Holder concentration
• Live market data (price, liquidity, volume)
All in one clean JSON. Sub-second response.
**5/7**
First check on any token starts a deep cluster trace in the background (returns "pending"). Re-check ~1–2 min later for the full picture. Real analysis takes real compute — we don't fake instant answers.
**6/7**
Pricing:
🆓 Free: 15 req/day, no card
💳 Pay-per-call: $0.07/call ($0.03 once subscribed)
📅 Subscription: $49 = 1000 calls/30 days
Paid in $MRDT / SOL / USDC via Solana Pay.
**7/7**
Works out of the box with ChatGPT Custom GPT Actions, LangChain/CrewAI agents, or any Python/TypeScript bot.
Same detection engine behind TNT House's token audits — just exposed as JSON for bots.
Get a free key 👇
🌐 https://t.co/0s4a2uqreM

[RiskDataAPI @RiskDataApiSol]

🔥 300 bots watching price and liquidity is impressive — но who's watching who's actually behind the token before the desk even opens a position?
🛡️ a у нас that's the missing layer — insider wallet clusters + honeypot check via one API call, before any bot in the swarm buys.
⚡ speed means nothing if the whole desk gets rugged together.

[RiskDataAPI @RiskDataApiSol]

@BNNBags @agentlayer_ai @USDC 🔥 gated data discovery for agents is exactly where this space needs to go.
🛡️ And we have RiskDataApi that's how our risk-scoring endpoint works too — agent pays x402, gets safety score back before it trades a Solana token.

[RiskDataAPI @RiskDataApiSol]

🚨 cool, your agent can buy stocks now. still can't tell you if the token it bought yesterday was a rug.
🤖 agentic finance means nothing if the agent trades blind — we built risk-scoring agents actually call before they buy: insider wallet clusters, honeypot check, LP lock, all in one API call.
⚡ AiFi without risk data is just gambling with extra steps.

[RiskDataAPI @RiskDataApiSol]

@Crypto_D10S 👍

[RiskDataAPI @RiskDataApiSol]

🕵️ When you audit a Solana token, how important is the deployer's history to your risk decision?

📊 How many tokens did they launch before?
💀 How many ended up rugged?
⚠️ Is this a recurring pattern?

🤖 Would your trading bot use this data?

Answers. 👇

1. 🔥 Critical — I need it.
2. 👍 Useful — nice to have.
3. 🤔 Depends on the data.
4. ❌ Not important.

Write your answer below in the comments. 👇

#Solana #AIagents #Crypto

[RiskDataAPI @RiskDataApiSol]

@TopNewToken 👍

[RiskDataAPI @RiskDataApiSol]

�� agentic commerce needs risk data as much as it needs payment rails.
🛡️ we're running risk-scoring for trading agents via x402 too — before an agent spends, it checks safety score + insider clusters, not just liquidity.
⚡ curious if x402scan tracks risk/data services separately from payment/commerce ones — feels like its own growing category.

[RiskDataAPI @RiskDataApiSol]

🔥 AiFi on Solana is exactly where risk infra needs to live too.
🛡️ agents paying per call need to trust what they're buying — we built x402-native risk scoring (insider clusters, honeypot, LP lock) so an agent can check before it trades, not after it gets rugged.
⚡ would love to be on that project list if it fits the AiFi stack.

[RiskDataAPI @RiskDataApiSol]

📈 makes sense — Solana's the only chain where x402 pay-per-call actually fits agent economics at scale.
🤖 we run risk-scoring for trading agents via x402 on Solana — no key, no signup, agent just pays and gets safety score + insider clusters back.
⚡ more facilitators shifting here = more infra like this becomes usable out of the box.

[RiskDataAPI @RiskDataApiSol]

🚨 Your trading bot checks liquidity. It doesn't check who's behind it.
🕵️ Insiders don't hold from the dev wallet. They fund fresh wallets that look empty on their own — until you trace the funder.
⚡ We built an API that does exactly that (RiskDataApi). One call before your agent buys:
🔹 Safety score 0-100
🔹 Insider wallet clusters (multi-hop funder tracing)
🔹 Honeypot + LP lock check
🔹 x402 support — no key, no signup, pay per call
🤖 Built for AI agents trading Solana memecoins. Plug it in, stop trading blind.
$0.02/call. 3 free/day, no key needed.
#Solana #AIagents #DeFi

[RiskDataAPI @RiskDataApiSol]

@Truunik @RobinhoodCrypto ◦ This is the right direction,
Agents shouldn't just execute swaps - they should evaluate risk before execution
On Solana, that means checking the token itself before the agent signs the transaction.

[RiskDataAPI @RiskDataApiSol]

@xona_agent @solana 🤖 Agents can pay autonomously.
But before an agent can safely transact with unknown tokens, it needs to understand the risk — not just the price. 🔍

[RiskDataAPI @RiskDataApiSol]

@Airdrops_one 🤖 That’s the real shift: humans watch charts, agents execute transactions.
The question becomes: what does the agent check before it signs?
Speed without token-level risk checks just makes bad decisions faster. ⚡

[RiskDataAPI @RiskDataApiSol]

🔥 x402 agents paying each other for data is exactly the pattern we built for.
⚡ our risk-scoring endpoint takes x402 too — agent hits it before a buy, pays per call, gets safety score + insider wallet clusters back, no key, no signup.
🤖 economics move faster when the agent doesn't have to stop and ask a human for an API key.

[RiskDataAPI @RiskDataApiSol]

�� "dev wallet clean" is the naive check.
🔍 insiders don't hold from the dev wallet — they fund fresh wallets that look empty on their own.
📊 LP burned + mint revoked + clean dev wallet still rugs when funder clusters are hidden.
🤖 that's the layer most bots skip. we built it as an API call.
🌐 You can check out RiskDataApi on our website; the link is in our profile.👆

[RiskDataAPI @RiskDataApiSol]

⚡ "rebuild" is right — most risk/fraud tooling was built for humans clicking buttons, not agents executing trades autonomously
🛡️ that's the layer we're rebuilding for Solana specifically with RiskDataAPI — an x402-priced MCP tool so a trading agent can check a token's risk before it pays, not after
🤖 the fintech stack changing is one thing, but nobody's agent should be sending money based on vibes

[RiskDataAPI @RiskDataApiSol]

⚡ x402 solves "the bot can pay" — the part still missing everywhere is "the bot knows what it's paying for is safe"
🛡️ we run RiskDataAPI as an x402-priced MCP tool for exactly this: agent hits our endpoint before it trades a Solana token, gets a risk score back, decides
🤖 feels like the natural next layer once bots are handling their own payments anyway

[RiskDataAPI @RiskDataApiSol]

🔍 fraud/token-distillation is the part every agent-commerce stack skips — they solve "is this payment authorized," nobody solves "is the thing being paid for even real"
🛡️ we built RiskDataAPI exactly for that gap — risk-scoring for Solana trading agents over MCP, so the agent itself checks before it pays, not after
💀 a wallet can be 100% authorized and still be sending money into a token run by 3 wallets pretending to be 20 — auth layer never catches that

[RiskDataAPI @RiskDataApiSol]

@SteveTheHead_ 🤖 letting an agent trade autonomously is exactly the setup where a token check matters most — you're not even in the loop when it buys
🔍 genuinely curious: does the agent screen for mint authority / holder concentration before it trades, or is that on you manually?

[RiskDataAPI @RiskDataApiSol]

exactly — and the funder trace doesn't stop at depth 1 either. we've seen wallets funded by a wallet that was funded by the same source three hops back, still showing up as "unique holders" in every basic scanner
the annoying part is building this at scale without flagging every CEX withdrawal as a cluster — that's where most naive implementations break

[RiskDataAPI @RiskDataApiSol]

Most Solana “risk tools” count wallets.

That’s the wrong object.

20 wallets holding 2% each looks decentralized.
Until you trace who funded them.
💀 Same first-funder = one actor. Not twenty buyers.

🛡️ That’s insider-cluster detection.
On-chain. Provable. Not a vibe score.

⚡ One GET. One JSON.

You get:
• Safety Score 0–100
• Insider clusters
• Honeypot risk
• LP lock status

🤖 Built for bots and agents — not dashboards.

🆓 3 checks with zero signup.
15/day free after that. No card.

🎯 Stop letting your bot buy the “distributed” supply.

#Solana #AIAgents #TokenSecurity #RiskDataAPI