Skip to main content

​
Pricing and included usage

These are the standard Swig subscription plans. Query access uses your existing organization subscription. 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; see subscription management 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

​
Make your first query

  1. Create an API key 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.
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. 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.