Skip to main content
Triqai uses a credit-based billing model. Each successful enrichment consumes credits from your monthly allocation.

​
How Credits Work

  • 1 credit = 1 enrichment: Each successfully enriched transaction consumes 1 credit
  • Monthly allocation: Credits are included in your plan and reset each billing cycle
  • No rollover: Unused credits don’t carry over to the next month
  • Overages available: Continue enriching beyond your allocation with per-request billing

​
Credits by Plan

Overage pricing is per 1,000 additional enrichments beyond your plan’s included credits.

​
When Credits Are Deducted

Credits are consumed when:
An enrichment request completes fully (success: true, partial: false)
Credits are not deducted when:
  • The enrichment returns a partial result (partial: true)
  • The request fails entirely (validation error, auth error, server error)
  • You hit your credit limit and overages are disabled
  • You query existing transactions (GET requests)
  • You fetch categories or entity details

​
Checking Your Balance

Monitor your credit usage in the dashboard:
  • Current credit balance
  • Usage history by day/week/month
  • Overage usage (if enabled)

​
Overage Billing

When you exceed your monthly credit allocation:

​
With Overages Disabled (Default)

  • Enrichment requests will fail with 402 Payment Required
  • Error code: insufficient_credits
  • You’ll need to wait for credits to reset or upgrade your plan

​
With Overages Enabled

  • Enrichment continues without interruption
  • Overage usage is tracked separately
  • Billed at the end of your billing cycle
To enable overages:
  1. Go to your dashboard settings
  2. Navigate to Billing > Overage Settings
  3. Toggle “Enable Overages”
Free tier accounts cannot enable overages. Upgrade to Starter or higher to continue enriching beyond your allocation.

​
Credit Reset

Your dashboard shows the exact credit allowance start and next reset, separately from plan renewal (or annual term end) and metered invoice dates. All financial boundaries use UTC, including the time of day; daily charts use UTC dates. The anniversary policy applies to new subscriptions and organizations migrated after review. Existing organizations retain their recorded schedule until then:
  • Monthly paid plans: The allowance follows the licensed plan’s exact Stripe service period. A purchase at 14:37 UTC does not reset early at midnight.
  • Annual plans: One full monthly allowance is available in each eligible monthly anniversary period within the paid service term, including a final partial month. The annual payment does not issue twelve allowances at once.
  • Free tier: Monthly allowances follow the original organization or free-plan anniversary, including its UTC time.
Days 29–31 are preserved: January 31 becomes February 28 (29 in leap years), then March 31. Local daylight-saving changes do not move these UTC boundaries. Unused plan credits do not roll over. Gift and additional credits retain their own expiry dates. If a reset is delayed, the job grants only the current eligible allowance and skips expired missed periods. New requests pause at the allowance boundary until the reset is ready; there is no additional spending entitlement during an outage. A request admitted before the boundary settles against its original allowance even if it completes later. Job execution time does not change period ownership.

​
Monitoring Usage

The dashboard provides real-time visibility into:
  • Credits remaining this period
  • Usage trends over time
  • Overage consumption (if applicable)
Display credit usage on dashboard can be delayed by max 5 minutes

​
Optimizing Credit Usage

Check if you’ve already enriched similar transactions. Transactions with the same raw title in the same country often produce identical results.
The playground is free and doesn’t consume credits. Use it for exploration and testing.
If you have many identical transactions (e.g., recurring payments), enrich one and apply the result to all.

​
Upgrading Your Plan

If you consistently need more credits:

Compare Plans

View all plans and included credits

Contact Sales

Discuss custom enterprise pricing

​
FAQ

One enrichment request that returns a fully successful result (partial: false) consumes one credit. Partial results do not consume credits.
No. Fetching transaction history, categories, or entity details does not consume credits. Only POST requests to the enrichment endpoint use credits.
Partial results (where some enrichers succeed but others fail) do not consume credits. Only fully successful enrichments are charged.
Credits are non-refundable but reset monthly. Consider adjusting your plan if you consistently have excess credits.
Overage usage is calculated at the end of your billing cycle and charged to your payment method on file.

​
Next Steps

Rate Limits

Understand request rate limits

Pricing

View plan details and pricing