Core conversion model: 1 USD = 3,913.89 credits (1 API call = 1 credit = $0.0002555).
Legal and policy documents on docs.hefitapi.com are authoritative and are not overridden by this page.
For validation and first integrations.
Base volume package
thfa_starter_tier
Higher performance profile
thfa_starter_tier_go
For production workloads and traffic.
Standard production volume
thfa_standard_tier
Enhanced throughput capacity
thfa_standard_tier_go
Scale rapidly with high concurrency.
Large scale traffic capacity
thfa_power_tier
Maximum burst concurrency
thfa_power_tier_go
Ultimate enterprise volume & support.
High volume data operations
thfa_business_tier
Enterprise-grade throughput
thfa_business_tier_go
Purchase credits in the dashboard and consume by request. Organization Admin and Developer API keys consume credits, while Finance can monitor balances, forecast burn, and replenish credits without API execution access.
For sustained enterprise workloads, contact us for dedicated onboarding, volume pricing, support terms, and private deployment options. Direct traffic on `api.hefitapi.com` is tuned for high concurrency and burst traffic beyond marketplace routing constraints.
Enter USD to estimate credits and total requests. (1 credit = 1 request)
Credits: 39,139
Requests: 39,139
Estimated rate: $0.0002555 x request
Use this quick estimator to align projected spend with request demand before launch and during traffic spikes.
Billing is usage-based. You buy credits and consume them through API calls.
The base model is 1 USD = 3,913.89 credits, with 1 request consuming 1 credit.
Credit terms can depend on commercial agreements. For enterprise plans, confirm terms with the sales team.
Yes. The dashboard exposes usage windows, endpoint activity, and credit burn so finance and platform teams can react before limits are hit.
Yes. High-volume teams can request custom commercial terms and support agreements.
Yes. The public infrastructure is designed for high concurrency and supports up to 80+ million monthly API hits.
Yes for direct host integrations. You can request responses in `en`, `fr`, `es`, `de`, `pt`, `ja`, `hi`, `ar`, `bn`, `gu`, `id`, `it`, `ko`, `mr`, `nl`, `pa`, `pl`, `ro`, `ru`, `ta`, `te`, `th`, `tr`, `ur`, `vi`, `zh` using the `lang` query parameter.
Yes. If you need infrastructure isolated from the public environment, contact us for private enterprise deployment and SLA agreements.