# 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.

Access: All plans; stream-session inspection requires eligible streaming access

[Compare plans and subscribe](https://madeonsol.com/pricing#pricing)

Author: 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 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

| Plan | REST / day | Standard sockets | DEX sockets | Webhooks |
| --- | ---: | ---: | ---: | ---: |
| Free | 200 | 0 | 0 | 0 |
| Pro | 10000 | 2 | 0 | 3 |
| Ultra | 100000 | 5 | 3 | 10 |
| Business | 500000 | 15 | 6 | 30 |

## Account quotas

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

## Inspect stream ownership (Pro and above)

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

## Forecast upstream reads (standalone JavaScript)

~~~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

- Count frontend requests as upstream REST demand. Fix: Measure actual backend calls after caching and coalescing.

- Use /me as an exact cross-worker billing ledger. Fix: Keep independent request telemetry and interpret the inspection response within its implementation limits.

- Upgrade only by daily quota. Fix: 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](https://madeonsol.com/docs/account)
- [Reduce MadeOnSol API calls with safe backend caching](https://madeonsol.com/docs/caching)
- [Scale a MadeOnSol terminal to multiple viewers](https://madeonsol.com/docs/terminal-at-scale)

## Match your plan to your workload

Compare capacity, channel access and display rights before launching.

[Compare plans and subscribe](https://madeonsol.com/pricing#pricing)

## Related reference

- [Developer dashboard](https://madeonsol.com/developer)
- [API tier comparison](https://madeonsol.com/api-docs#tier-comparison)
- [Errors and rate limits](https://madeonsol.com/api-docs#errors)
- [Plan comparison](https://madeonsol.com/pricing)
- [Terms and display rights](https://madeonsol.com/terms)

[Canonical guide](https://madeonsol.com/docs/usage-planning)
