Every Tuteliq API call consumes credits. Credit costs vary by endpoint based on processing complexity. Your current balance and usage are always available through the dashboard and the API.
Per-endpoint costs
Core Safety
| Endpoint | Credits | Notes |
|---|
detectBullying | 1 | Single text analysis |
detectUnsafe | 1 | Single text analysis |
detectGrooming | 1 per 10 msgs | ceil(messages / 10), minimum 1 |
Fraud Detection
| Endpoint | Credits | Notes |
|---|
detectSocialEngineering | 1 | Social engineering tactic detection |
detectAppFraud | 1 | Fraudulent app/download detection |
detectRomanceScam | 1 | Romance scam pattern detection |
detectMuleRecruitment | 1 | Money mule recruitment detection |
Safety Extended
| Endpoint | Credits | Notes |
|---|
detectGamblingHarm | 1 | Gambling harm detection |
detectCoerciveControl | 1 | Coercive control detection |
detectVulnerabilityExploitation | 1 | Vulnerability exploitation + cross-endpoint modifier |
detectRadicalisation | 1 | Radicalisation indicator detection |
Multi-Endpoint Analysis
| Endpoint | Credits | Notes |
|---|
analyseMulti | Sum of endpoints | Fan-out to up to 10 endpoints in one call |
Analysis & Guidance
| Endpoint | Credits | Notes |
|---|
analyzeEmotions | 1 per 10 msgs | ceil(messages / 10), minimum 1 |
getActionPlan | 2 | Longer generation |
generateReport | 3 | Structured output |
Verification (Beta)
| Endpoint | Credits | Notes |
|---|
verifyAge | 5 | Document analysis + biometric estimation (Pro tier and above) |
verifyIdentity | 10 | Document verification + liveness detection (Business tier and above) |
Document Analysis
| Endpoint | Credits | Notes |
|---|
analyzeDocument | Dynamic | max(3, pages_analyzed × endpoint_count) — minimum 3 credits |
Document analysis uses per-page, per-endpoint pricing. Each page-endpoint combination costs 1 credit (matching text detection), with a minimum of 3 credits to cover extraction overhead. See Document Analysis for detailed examples.
| Endpoint | Credits | Notes |
|---|
analyzeVoice | 5 | Transcription + analysis |
analyzeImage | 3 | Vision + OCR + analysis |
analyzeVideo | 10 | Frame extraction + per-frame vision |
| Voice stream (per flush) | 1 | Real-time transcription + analysis |
| Video stream (per frame) | 3 | Per-frame vision analysis |
For conversation-based endpoints (detectGrooming, analyzeEmotions), credits scale with message count. A 25-message conversation costs ceil(25 / 10) = 3 credits.
Batch processing example
When submitting a batch of 500 text messages through detectUnsafe:
500 messages x 1 credit = 500 credits
For a batch of 200 messages through detectGrooming with 15 messages per conversation:
200 conversations x ceil(15 / 10) = 200 x 2 = 400 credits
Purchasing credits
Credits can be purchased from the Tuteliq Dashboard. Navigate to Billing > Purchase Credits to top up your balance. Plans include monthly credit allowances, with overage billing available for high-volume usage.
Tracking usage
Response body
Every API response includes a credits_used field showing the credits consumed by that request:
{
"detected": true,
"severity": 0.85,
"confidence": 0.91,
"risk_score": 0.87,
"categories": [{ "tag": "AUTH_IMPERSONATION", "label": "Authority Impersonation", "confidence": 0.92 }],
"credits_used": 1
}
Each response also includes the X-Credits-Remaining header with your current balance:
X-Credits-Remaining: 9472
Usage endpoints
Check your credit balance and historical usage programmatically via the Usage API:
const usage = await tuteliq.getUsage();
console.log(usage.credits_remaining);
console.log(usage.credits_used_today);
Low-balance alerts
Configure low-balance notifications in the Dashboard under Settings > Alerts. You can set a credit threshold (e.g., 100 credits remaining) and receive email or webhook notifications before you run out.
What happens when credits run out
When your balance reaches zero, API requests return a 402 Payment Required error. Upgrade your plan or purchase additional credits from the Dashboard to resume service.