Buy Pepiko credits once, then spend them across classification, moderation, policy routing, and privacy APIs. Pricing scales with input volume, not confusing request bundles.
Credits make pricing predictable across products. Each API call consumes credits based on the product used and the amount of text processed.
A standard safety unit covers up to 1,000 input tokens. Larger requests are rounded up to the next 1,000-token block.
For local testing and prototypes.
$0/moFor early production apps.
$49/moFor teams scaling traffic.
$299/moFor high-volume platforms.
CustomCredits are metered per request and per 1,000-token block, so heavier workflows are priced fairly.
| Product | Metering unit | Credits | Best for |
|---|---|---|---|
| Child Safety ClassificationCore child-risk detection | Per request / 1K input tokens | 1 credit | Kids apps, AI tutors, chatbots |
| Prompt ClassifierIntent and category classification | Per request / 1K input tokens | 0.5 credits | Routing prompts before response generation |
| Moderation APIInput and output safety review | Per moderation pass / 1K tokens | 1.5 credits | Chat, UGC, classroom tools, community content |
| Policy RoutePolicy bucket and recommended action | Per policy decision | 0.75 credits | Blocked, allowed, safe-completion, escalation routes |
| PII DetectionPersonal and sensitive data detection | Per scan / 1K tokens | 0.8 credits | Privacy checks before storage or model calls |
A 1,600-token message sent through Child Safety Classification uses 2 credits. The same message through Moderation API uses 3 credits.
