Credits
Credits are Surflux's unified billing unit for all API requests, gRPC calls, and data streaming. Everything on the platform consumes credits, making usage tracking simple and predictable.
How Credits Work
Your plan provides a monthly credit allocation that resets on your billing anniversary.
Monthly Allocations by Plan
| Plan | Monthly Credits |
|---|---|
| Free | 250,000 |
| Builder | 5,000,000 |
| Scale | 20,000,000 |
| Pro | 50,000,000 |
| Enterprise | Custom (100M-1B+) |
Credits reset at the start of each billing cycle and do not roll over.
Credit Costs
All Surflux services consume credits. Costs are fixed per request for APIs and proportional to data transferred for streams.
NFT Indexing API
Each endpoint has a fixed credit cost based on computational complexity:
| Endpoint | Credit Cost | Description |
|---|---|---|
GET /nfts/:objectId | 5 | Retrieve single NFT by object ID |
GET /nfts/address/:address | 10 | Get all NFTs owned by an address |
GET /kiosks/:id/nfts | 10 | Get NFTs in a Kiosk |
GET /nfts/collection/:type | 15 | Query NFTs within a collection |
GET /nfts/collection/:type/holders | 50 | Get holder distribution for a collection |
Example: Fetching one wallet's NFT gallery (address + 10 objects):
10 (address) + (10 × 5) (objects) = 60 credits per session
DeepBook Indexing API
Trading data endpoints cost more due to real-time indexing requirements:
| Endpoint | Credit Cost | Description |
|---|---|---|
GET /deepbook/get_pools | 5 | List all trading pools |
GET /deepbook/:poolName/trades | 20 | Historical trade executions |
GET /deepbook/:poolName/ohlcv/:timeframe | 25 | Candlestick/OHLCV data |
GET /deepbook/:poolName/order-book-depth | 30 | Current order book state |
Example: Loading a trading dashboard (pools + order book + recent trades):
5 (pools) + 30 (order book) + 20 (trades) = 55 credits per load
Flux Streams
Unlike per-request billing, Flux Streams charge based on data transferred:
1 KB = 1 credit
Streams charge only for the bytes you receive. Surflux filters events server-side, so you never pay for irrelevant data.
Typical stream usage:
| Stream Type | Daily Data | Monthly Credits |
|---|---|---|
| DeepBook (SUI/USDC) | 120-130 MB | ~3,600,000-3,900,000 |
| Cetus Protocol | 28 MB | ~840,000 |
| Navi Protocol | 88 MB | ~2,640,000 |
| Suilend Protocol | 245 MB | ~7,350,000 |
| Momentum Protocol | 363 MB | ~10,890,000 |
Stream costs scale with protocol activity. A quiet custom stream might use less than 100k credits/month, while DeepBook's high-frequency trading data uses ~3.9M/month.
gRPC API
gRPC calls have a fixed cost regardless of the method called:
5 credits per request
This covers the cost of maintaining high-performance gRPC infrastructure and handling Protocol Buffer serialization.
Understanding Your Usage
Flux Streams
Flux Streams consume credits based on data transferred: 1 KB = 1 credit.
A 24/7 DeepBook stream (SUI/USDC) typically uses 3.6-3.9M credits/month (120-130 MB/day).
Other protocol examples:
- Cetus: ~840k credits/month (fits comfortably into Free plan)
- Navi: ~2.6M credits/month (basic coverage with Builder)
- Suilend: ~7.3M credits/month (good coverage with 2 streams on Scale)
- Momentum: ~10M credits/month (optimal coverage with 4-5 streams on Pro)
Your stream usage depends on the protocol's activity level and complexity.
Indexing APIs
Each API endpoint has a fixed credit cost:
NFT Indexing:
GET /nfts/address/:address- 10 creditsGET /nfts/:objectId- 5 creditsGET /nfts/collection/:type- 15 creditsGET /nfts/collection/:type/holders- 50 creditsGET /kiosks/:id/nfts- 10 credits
DeepBook Indexing:
GET /deepbook/get_pools- 5 creditsGET /deepbook/:poolName/trades- 20 creditsGET /deepbook/:poolName/order-book-depth- 30 creditsGET /deepbook/:poolName/ohlcv/:timeframe- 25 credits
gRPC:
- Fixed cost: 5 credits per request
Usage Examples
NFT Wallet Gallery
- One address read (10) + 10 object details (10×5) = ~60 credits/session
- At 1,000 sessions/day → ~1.8M credits/month (Builder tier)
Collection Explorer
- One collection page (15) + 30 object details (30×5) = ~165 credits/view
- At 10,000 pageviews/day → ~49.5M credits/month (Pro tier)
Trading Dashboard
- 1 DeepBook stream (~3.9M/month) + periodic order book checks
- Fits comfortably in Builder tier with room for other queries
Frequently Asked Questions
Do credits expire?
Yes. Credits reset monthly on your billing anniversary and do not roll over. Enterprise plans can negotiate custom terms.
Can I purchase additional credits?
Enterprise customers can negotiate prepaid credit packages with volume discounts.
What if I downgrade mid-cycle?
Downgrades take effect at your next billing cycle. You'll continue to have access to your current tier's credits until then.
How are stream credits calculated?
Streams charge 1 credit per KB of uncompressed data transferred. Compression savings are not passed through; you're charged for the raw event size.
Why are some endpoints more expensive?
Endpoint costs reflect computational complexity, indexing requirements, and real-time data processing. Holder distribution queries (/holders, 50 credits) aggregate data across thousands of wallets, while simple object lookups (5 credits) are direct key-value retrievals.
Next Steps
- View Plans — Compare tiers and pricing
- Rate Limits — Understand RPS caps
- Create Account — Start building
- Dashboard — Monitor usage in real-time