MadeOnSolMade on Sol

Data APIs

Solana Data APIRobinhood Chain API

Intelligence

Telegram AlertsKOL TrackerWallet ScannerToken LookupDeployer Hunter
Trading BotsTrading TerminalsWallet TrackingToken Scanners
View all solutions
Optimization guidesAPI DocsWebSocket StreamingMCP & SDKsx402 for AI AgentsAgent Intelligence Gateway
Discover ToolsCompare ToolsSubmit a ToolAdvertiseBlog
Pricing
Get real-time feedsSign in
MadeOnSolMade on Sol

Solana and Robinhood Chain intelligence — KOL wallet tracking, deployer intelligence, all-DEX trade streams, and a developer API. Discover, compare, and build.

Product

  • Solana Data API
  • Solana Wallet Checker
  • Robinhood Chain Wallet Checker
  • Robinhood Chain API
  • Robinhood Chain x402
  • MCP Servers & SDKs
  • x402 for AI Agents
  • Agent Intelligence Gateway
  • Pricing
  • Enterprise / For Businesses

Solutions

  • Trading Bots
  • Wallet Tracking
  • Copy Trading
  • Token Scanners
  • Trading Terminals
  • DEX Data
  • Smart Money
  • Token Risk
  • AI Agents
  • ShredPrism Stream
  • View all solutions

Developers

  • Optimization guides
  • API Docs
  • WebSocket Streaming
  • Changelog
  • API Status
  • Latency Benchmarks
  • Data Integrity
  • Data Dictionary
  • Methodology

Resources

  • All Tools
  • Compare Tools
  • Best Trading Bots
  • Best DEXs
  • Best Wallets
  • Best Analytics
  • Best DeFi
  • Best Snipers
  • Blog
  • Blog Archive
  • Signal Scorecard
  • Tool Uptime
  • Community
  • Submit a Tool
  • Advertise

Company

  • About
  • Contact
  • Security
  • Privacy
  • Terms
  • DPA
  • Disclaimer

© 2026 MadeOnSol

MadeOnSol — eenmanszaak, Hulshout, Belgium · KBO/BTW BE 1039.535.538 (art. 56bis, no VAT charged)

Runs on our own dedicated EU servers — self-hosted data stack, own Robinhood Chain node · security

Powered by:constant·k — Private Solana RPC Services
Browse all guides
Optimization guidesValidate a KOL feed before increasing request volumeProcess webhook retries without duplicate effectsRecover a WebSocket feed after a disconnectReduce REST polling in a trading terminalMerge live candles with historical OHLCVCache KOL rankings while streaming tradesBudget REST calls and WebSocket slotsTake a MadeOnSol API integration from prototype to productionBuild reliable MadeOnSol WebSocket recoveryReduce MadeOnSol API calls with safe backend cachingScale a MadeOnSol terminal to multiple viewersInterpret token amounts, timestamps and data quality correctlyBuild reliable trading alerts with MadeOnSol dataMeasure MadeOnSol usage and choose the right API planAPI reference
Optimization guidesValidate a KOL feed before increasing request volumeProcess webhook retries without duplicate effectsRecover a WebSocket feed after a disconnectReduce REST polling in a trading terminalMerge live candles with historical OHLCVCache KOL rankings while streaming tradesBudget REST calls and WebSocket slotsTake a MadeOnSol API integration from prototype to productionBuild reliable MadeOnSol WebSocket recoveryReduce MadeOnSol API calls with safe backend cachingScale a MadeOnSol terminal to multiple viewersInterpret token amounts, timestamps and data quality correctlyBuild reliable trading alerts with MadeOnSol dataMeasure MadeOnSol usage and choose the right API planAPI reference
Optimization guidesMeasure MadeOnSol usage and choose the right API plan

All plans; stream-session inspection requires eligible streaming access · Compare plans and subscribe

Measure MadeOnSol usage and choose the right API plan

Estimate REST demand, inspect account quotas and streaming sessions, and choose a MadeOnSol tier from measured capacity and display needs.

By MadeOnSol · Updated 2026-11-17

Integration choice

Measure the workload before choosing capacity. Separate daily REST demand, bursts, standard sockets, DEX sockets and per-connection subscription limits. Check display rights independently; a plan with enough calls is not automatically licensed for every distribution model.

Before you startImplementation stepsKnow what each number measuresBudget requests and bursts separatelyChoose by the tightest constraintCode examplesCommon mistakesVerify your integrationProduction checklistQuestions

Before you start

  • A representative watchlist and expected active hours per day.
  • Telemetry for upstream requests and concurrent sockets, separated from frontend requests.

Implementation steps

  1. Record upstream requests by route, result and consumer over a representative session. Count retries and recovery reads, not only successful responses.
  2. Inspect GET /api/v1/me for tier, quota and feature information. Use your own request telemetry as the workload record; account inspection is not a replacement for a distributed usage ledger.
  3. Calculate expected daily demand from distinct uncached queries and their active duration. Add initial reads, recovery work and an explicit safety margin.
  4. Measure peak overlapping stream sessions, including deploy overlap. Use the session endpoint to investigate ownership rather than repeatedly evicting healthy processes.
  5. Compare all limiting dimensions and licensing needs with the current plan table and terms. Optimize redundant work, then upgrade when the remaining workload or rights require it.

Know what each number measures

GET /api/v1/me exposes quota.daily, quota.burst and feature limits. Its usage state is read from an in-process limiter, while daily enforcement also uses a persistent limiter shared across workers. Treat the reported usage as an inspection signal, not an authoritative aggregate across processes or restarts.

The stream-token and stream-session routes have separate control-plane rate-limit buckets in the current implementation. They are not a licence to reconnect without restraint. Inspect response headers and the operation that was throttled before changing your polling schedule.

Budget requests and bursts separately

One uncached read every five seconds for a full day is 17,280 requests before retries. Shared caching changes the number of distinct upstream queries; adding a viewer to an existing shared watch need not add another polling loop.

A daily estimate alone does not cover a cold start where many panels load simultaneously. Queue or stagger reads and reserve headroom for reconnect repair. The calculator’s safety factor is a planning choice and does not change provider limits.

Choose by the tightest constraint

The limits table below is generated from the application’s subscription configuration, so it updates with that source. Standard-stream sockets and DEX sockets are separate capacities. Named-subscription caps and channel eligibility must be checked separately through stream discovery and reference documentation.

Use the pricing page for current prices and purchase options. Under the current terms, Free, Pro and Ultra cover internal use; Business adds display within one branded product, with attribution. Redistribution, white-label and multi-product use require an Enterprise agreement.

Self-serve account limits
PlanREST / dayStandard socketsDEX socketsWebhooks
Free200000
Pro10,000203
Ultra100,0005310
Business500,00015630

Code examples

Account quotas

curl -H "Authorization: Bearer $MADEONSOL_API_KEY" "https://madeonsol.com/api/v1/me"

Inspect stream ownership (Pro and above)

curl -H "Authorization: Bearer $MADEONSOL_API_KEY" "https://madeonsol.com/api/v1/stream/sessions"

Forecast upstream reads (standalone JavaScript)

// Application forecast; these are workload inputs, not plan limits.
function estimateDailyReads({ activeSeconds, intervalSeconds, distinctQueries,
  initialReads = 0, recoveryReads = 0, retryReads = 0, safetyFactor = 1.2 }) {
  const counts = [activeSeconds, distinctQueries, initialReads, recoveryReads, retryReads];
  if (counts.some(n => !Number.isFinite(n) || n < 0) ||
      !Number.isFinite(intervalSeconds) || intervalSeconds <= 0 ||
      !Number.isFinite(safetyFactor) || safetyFactor < 1) throw new Error("Invalid workload");
  // Recurring reads plus separately counted initial/recovery/retry work.
  const recurring = Math.ceil(activeSeconds / intervalSeconds) * distinctQueries;
  return Math.ceil((recurring + initialReads + recoveryReads + retryReads) * safetyFactor);
}
console.log(estimateDailyReads({ activeSeconds: 86400, intervalSeconds: 5,
  distinctQueries: 1, safetyFactor: 1 })); // 17280

Common mistakes and fixes

Common integration mistakes and recommended fixes
MistakeRecommended fix
Count frontend requests as upstream REST demand.Measure actual backend calls after caching and coalescing.
Use /me as an exact cross-worker billing ledger.Keep independent request telemetry and interpret the inspection response within its implementation limits.
Upgrade only by daily quota.Also check bursts, socket counts, subscription caps, channels and display rights.

Verify your integration

Run the same watchlist with one viewer and several equivalent viewers. Confirm upstream requests grow with distinct work rather than browser count. Reconnect once, include the repair traffic in the estimate, and compare observed peaks against the account’s limits.

Production checklist

  • Forecast includes snapshots, retries and recovery.
  • Peak burst and overlapping socket demand measured.
  • No ownership-blind session eviction loop.
  • Capacity and licence both match the product.

Frequently asked questions

Will twice as many viewers use twice as many API calls?

Not necessarily. Equivalent viewers can share backend reads and streams. Distinct watchlists, filters or permissions can add real upstream work.

Where should I check current prices?

Use the pricing page linked from this guide. The guide focuses on measurement and uses shared application configuration for its limits table.

Continue building

  • Budget REST calls and WebSocket slots
  • Reduce MadeOnSol API calls with safe backend caching
  • Scale a MadeOnSol terminal to multiple viewers

Match your plan to your workload

Compare capacity, channel access and display rights before launching.

Compare plans and subscribe
Read this guide as Markdown
Developer dashboardAPI tier comparisonErrors and rate limitsPlan comparisonTerms and display rights