Simple Unit Economics

Usage pricing
without forced subscriptions.

Core conversion model: 1 USD = 3,913.89 credits. One API call consumes one credit, equivalent to $0.0002555 per request.

Legal and policy documents on docs.hefitapi.com are authoritative and are not overridden by this page.

StarterFor validation and first integrations.
$10 USD
39,140 API Credits
Base volume package
thfa_starter_tier
$20 USD
78,280 API Credits
Higher performance profile
thfa_starter_tier_go
  • Dashboard access
  • Email support
Get Started
StandardFor production workloads and traffic.
$50 USD
195,700 API Credits
Standard production volume
thfa_standard_tier
$100 USD
391,400 API Credits
Enhanced throughput capacity
thfa_standard_tier_go
  • Priority support
  • Higher rate ceilings
Get Started
BusinessUltimate enterprise volume & support.
$300 USD
1,174,200 API Credits
High volume data operations
thfa_business_tier
$500 USD
1,960,000 API Credits
Enterprise-grade throughput
thfa_business_tier_go
  • SLA guarantees
  • Custom contracting
Talk to Sales

How Billing Works

Credits follow requests.

Purchase credits in the dashboard and consume them by request. Organization Admin and Developer keys consume credits, while Finance can monitor balances, forecast burn and replenish credits without API execution access.

Billing roles

Custom Contract

Sustained enterprise workloads.

For high-volume environments, contact us for dedicated onboarding, volume pricing, support terms and private deployment options. Direct traffic is tuned for high concurrency beyond marketplace routing constraints.

Talk to salesCompute grid

Conversion Calculator

Estimate request capacity.

Enter a USD amount to estimate credits and total requests at the current core conversion.

1 credit = 1 request. Estimated rate: $0.0002555 × request.

39,139Credits
39,139Requests
$0.0002555Estimated unit rate per request

How to Use This Estimate

Plan traffic before launch and during spikes.

  • Plan monthly traffic envelopes by endpoint mix.
  • Map campaign spikes to burst-ready direct API capacity.
  • Reconcile spend in dashboard with request consumption.

Pricing FAQs

Billing, volume and deployment.

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. The 26 supported locale keys are available through the lang query parameter.
Yes. Teams that need infrastructure isolated from the public environment can request private enterprise deployment and SLA agreements.