Beyond the Token Price: The Hidden Fees to Check Before Committing to Any LLM Aggregator
When choosing an LLM API aggregator, the advertised token price is only part of the cost. This article explains the hidden fees—deposit minimums, withdrawal fees, failed-call billing, and cache-read pricing—that can affect your total spend. It provides practical steps to verify each on a USDC-funded account, helping you make an informed decision beyond the headline rate.
Beyond the Token Price: The Hidden Fees to Check Before Committing to Any LLM Aggregator
When evaluating an LLM API aggregator, it's natural to focus on the token price. But the total cost of using a service often includes additional fees that aren't immediately obvious. These hidden costs can significantly impact your budget, especially if you're scaling usage or running many small requests. This guide covers the key non-token cost lines to examine and how to verify them on a USDC-funded account.
Deposit Minimums
Many aggregators require a minimum deposit to activate your account or unlock certain features. A high minimum can lock up capital you might prefer to keep liquid.
- What to check: The smallest amount you can deposit and whether it varies by payment method.
- How to verify: On a USDC-funded platform, attempt a deposit below the stated minimum to see if it's rejected. Check the deposit page for any tiered thresholds.
Withdrawal Fees
Withdrawal fees are charged when you move funds out of your aggregator account. They can be fixed or percentage-based and may differ by network.
- What to check: The fee for withdrawing USDC, including any network transaction costs.
- How to verify: Initiate a small withdrawal and observe the deducted amount. Review the fee schedule, which should be publicly available.
Failed-Call Billing
Not all API calls succeed. Some aggregators bill for failed calls due to timeouts, rate limits, or invalid requests. This can inflate costs unexpectedly.
- What to check: The policy on failed calls: are you charged for partial processing, retries, or errors?
- How to verify: Purposely trigger a failed call (e.g., with an invalid parameter) and check your usage statement to see if it was billed.
Cache-Read Pricing
Caching can reduce costs for repeated prompts, but cache reads may be priced differently from standard input tokens. Some aggregators charge a premium for cache hits.
- What to check: The cost per cache-read token versus regular input tokens and whether caching is enabled by default.
- How to verify: Send the same prompt twice and compare the billed amounts. The second call should reflect cache-read pricing if caching is active.
How to Verify on a USDC-Funded Account
Verifying these fees requires a methodical approach. Here's a step-by-step process:
- Start small: Deposit a minimal amount of USDC to test the deposit process and minimums.
- Review the fee schedule: Look for a public page detailing all fees, including deposit, withdrawal, and special pricing.
- Run controlled tests: Make API calls that trigger each fee type (e.g., a failed call, a cached prompt) and monitor your balance.
- Check usage logs: Ensure the aggregator provides detailed logs showing how each call was billed.
- Withdraw a small amount: Test the withdrawal process to confirm the fee and speed.
Why This Matters
Ignoring these fees can lead to a higher effective cost per token than advertised. For example, if you're charged for failed calls, your error rate directly impacts your bill. Similarly, high withdrawal fees reduce the value of your remaining balance when you cash out. By understanding and verifying these costs, you can choose an aggregator that aligns with your usage patterns and budget.
Example: USDC on Base with No KYC
Some aggregators, like the one described here, allow USDC deposits on Base with no KYC. They charge users the official token price multiplied by 1.3, and key contributors receive credits at official price multiplied by 1.1 (or 1.2 for premium) in USDC. This model is transparent about the markup, but you should still check for additional fees beyond the token price. The same verification steps apply: test deposits, withdrawals, failed calls, and cache reads to ensure no surprises.
Conclusion
The token price is just one component of your total LLM API costs. Deposit minimums, withdrawal fees, failed-call billing, and cache-read pricing can add up. Always verify these on a USDC-funded account before committing. A few small tests can save you significant money and frustration in the long run.