> ## Documentation Index
> Fetch the complete documentation index at: https://build.onswig.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Pricing and Quotas

> Compare monthly plans, included usage, and API quotas.

## Pricing and included usage

These are the standard Swig subscription plans. Query access uses your existing
organization subscription.

| Plan | Monthly price (USD) | Included API requests | DEX queries per calendar month | API-request overage |
| :- | -: | -: | -: | :- |
| Free | \$0 | 50,000 | 10,000 | Hard cap; upgrade to continue |
| Pro | \$39 | 100,000 | 2,000,000 | \$2.50 per 1,000 additional requests |
| Ultra | \$399 | 250,000 | 10,000,000 | \$2.25 per 1,000 additional requests |
| Enterprise | Custom | 500,000+ | 10,000,000 | From \$2.00 per 1,000 additional requests |

Enterprise API-request allowances and pricing depend on your agreement. The DEX
query cap is separate. Check your organization's plan and billing period in the
[Developer Portal](https://dashboard.onswig.com); see
[subscription management](https://build.onswig.com/examples/dev-portal/subscriptions-billing) to change plans.

### API requests

* Wallet, yield, ramp, rent-recipient, and paymaster reads each consume one API
  request. Paginated reads consume one request per page.
* This allowance is shared with other metered API operations, such as transaction
  preparation and sponsorship, and attributed IdP requests. It is not reserved
  for reads.
* Free organizations stop at 50,000 requests in a UTC calendar month. Paid plans
  continue beyond their included requests with the API-request overage above.
* Subscription invoices follow your billing period. The Free admission cap
  resets at 00:00 UTC on the first day of each calendar month.

### DEX queries

* Each DEX transaction-list, transaction-detail, or position-list call consumes
  one DEX query and does not consume the API-request allowance.
* The quota is shared by the organization's API keys and networks. It resets
  at 00:00 UTC on the first day of each calendar month.
* Every plan has a hard DEX cap. At the cap, requests return HTTP `429`
  (`RESOURCE_EXHAUSTED`); API-request overage does not buy more DEX queries.
* Use a plan with a larger quota or wait for the next calendar month. Contact
  Swig if your required volume exceeds the published plans.

### What counts

Usage is counted when an authenticated request is admitted, before the operation
finishes. Retries, empty results, and admitted requests that later return errors
such as `400` or `404` still count. A rejected API key or exhausted quota does
not add an admitted request. Each returned row is not a separate charge.

For example, reading token balances once and three pages of DEX history uses
**one API request and three DEX queries**. Retrying one DEX page adds one DEX query.

## What you can query

| Section | Available data | Usage allowance |
| :- | :- | :- |
| [Wallets](https://build.onswig.com/query/wallets) | Token movements, roles, policies, rent recipient | API requests |
| [Balances](https://build.onswig.com/query/balances.md) | Native SOL and token holdings, total USD value | API requests |
| [DEX activity](https://build.onswig.com/query/dex.md) | Indexed trades and liquidity actions, individual transactions, latest positions | DEX queries |
| [Yield](https://build.onswig.com/query/yield.md) | Validators and rates, reward estimates, positions, totals, recorded rewards | API requests |
| [Ramp](https://build.onswig.com/query/ramp.md) | Supported countries and assets, buy/sell quotes, order status | API requests |
| [Paymasters](https://build.onswig.com/query/paymasters.md) | API and IdP paymaster configuration and SOL balances | API requests |
| [Public wallets and identity](https://build.onswig.com/query/public) | Wallet lookup/status and identity verification keys | Public-route rules described in that guide |

## Make your first query

1. [Create an API key](https://build.onswig.com/examples/dev-portal/create-api-key.md) for your organization.
2. Keep it on your trusted server and send it as a bearer token.
3. Choose a query guide above and use its network, filters, and pagination rules.

```bash theme={null}
curl "https://api.onswig.com/wallet/swig/<swig-config-address>/token-balances?network=NETWORK_MAINNET" \
  -H "Authorization: Bearer $SWIG_API_KEY"
```

This call consumes one API request. Replace the config-address placeholder with
your Swig config address. The public wallet and identity routes use their own
client boundary and do not require this server API key.

For SDK setup, use [Client setup](https://build.onswig.com/developer-sdk/integration-paths.md). For exact
request and response fields, follow each guide's REST reference. Indexed data
can lag chain state; each guide explains the available freshness signals.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.