x402solanaquality 0.45

Solana token intelligence API: safety analysis, holder networks, wallet profiling, and social research via x402 micropayments.

Price
per_call
Protocol
x402
Verified
no

What it does

Deepnets API provides AI-powered token intelligence for Solana SPL tokens. It exposes endpoints for token safety analysis (risk levels, mintable/freezable flags, critical risks, warnings), holder funding-network graphs that trace wallet relationships across multiple hops to uncover hidden concentration, full holder breakdowns with network bundles and individual holder percentages, wallet profiling (funding source, exchange attribution, tags), funding-network overviews, social research (Twitter/X, Telegram, website sentiment), watchlists of safety-screened high-volume tokens, flagged dangerous tokens, Streamflow vesting lock data, and Tibane staking stats.

The specific endpoint `/api/resolve-symbol` is listed but not documented in the OpenAPI spec or the Redocly docs. Its purpose appears to be resolving a token symbol or name to a Solana mint address, but this is inferred — no schema or response format is available for this particular path.

Payment is handled via the x402 protocol using USDC on Solana — no account is required. Most read endpoints cost $0.01 per call; full holder analysis endpoints cost $0.15 per call. Alternatively, users can authenticate with an API key (generated at deepnets.ai) where reads are included and new research jobs cost 1 credit (purchased by burning $DNET tokens). Rate limits for x402 callers are 30 requests per minute per source IP. The API also offers a WebSocket real-time token stream and async research job submission (API-key only).

Capabilities

solana-token-safetyholder-network-analysiswallet-funding-graphsocial-researchtoken-watchlistflagged-token-detectionwallet-profilingexchange-attributionbundle-detectionvesting-lock-datastaking-statssymbol-resolutionx402-usdc-payment

Use cases

  • Assess risk before buying a Solana token by checking safety level, holder concentration, and mintable/freezable flags
  • Investigate wallet networks to detect coordinated insider bundling or sybil attacks on a token
  • Discover trending safe tokens via the watchlist or identify dangerous tokens via the flagged-tokens feed
  • Perform social due diligence on a token's Twitter, Telegram, and website presence
  • Resolve a token symbol to its Solana mint address for downstream lookups

Fit

Best for

  • AI agents performing automated Solana token due diligence
  • Trading bots that need pre-trade safety checks on SPL tokens
  • Researchers investigating wallet funding networks and coordinated activity
  • Developers building Solana token dashboards with risk scoring

Not for

  • Non-Solana blockchains (Ethereum, Bitcoin, etc.) — this API is Solana-only
  • Real-time price feeds or DEX trading execution
  • Tokens that have never been analyzed by Deepnets (requires triggering async research first)

Quick start

# Resolve a token symbol to a mint address (x402, $0.01 USDC on Solana)
curl -i https://api.deepnets.ai/api/resolve-symbol?symbol=BONK
# Returns 402 with PAYMENT-REQUIRED header; use an x402 client to settle automatically.

Endpoint

Transporthttp
Protocolx402
Pay toBn7sLNmcL9ru5kt9gNwVn8e8Sx912dBTxiUBNiwjbiY8
CurrencyUSDC

Quality

0.45/ 1.00

The broader Deepnets API has a comprehensive OpenAPI spec and detailed Redocly docs, but the specific `/api/resolve-symbol` endpoint is not documented in either source — no schema, parameters, or response format are available. The probe returned 401 (not 402), suggesting the endpoint may require an API key or behaves differently from other x402 endpoints. Pricing and behavior for this specific path are inferred.

Warnings

  • The /api/resolve-symbol endpoint is NOT present in the published OpenAPI spec or Redocly documentation — its parameters and response schema are unknown.
  • Probe returned HTTP 401 on both GET and POST, not the expected 402 x402 challenge. This may indicate the endpoint requires API-key auth only, or it may not support x402 payment.
  • No example request or response can be provided for this specific endpoint due to missing documentation.
  • root_fetch_status was 404, which is expected for an API-only origin with no landing page.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-22 02:51:40Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access