Authentication
KPD splits requests into two tiers based on whether they carry a valid API key.
| Tier | Condition | Limit |
|---|---|---|
| free | No key (or invalid / expired / out of credits) | 7 requests per minute per IP |
| paid | Valid key + credit balance | Higher per-key limits, credits deducted per request |
Getting a key
You can issue one API key per account from the dashboard. The kpd_live_… key is shown only once at creation, so copy it somewhere safe — only its hash is stored on the server, and it can't be shown again.
Sending the key
Pass your key in a request header. Either style works:
X-API-Key: kpd_live_xxxxxxxxxxxx
or
Authorization: Bearer kpd_live_xxxxxxxxxxxx
Example:
curl -s -X POST https://harm-api.rhu.kr/detect \
-H 'Content-Type: application/json' \
-H 'X-API-Key: kpd_live_xxxxxxxxxxxx' \
-d '{"text":"판정할 문장"}'
Credits and billing
A freshly issued key starts with a 0 balance, so it behaves like the free tier. Once you top up credits in the dashboard, the key becomes paid and 0.0135 credits are deducted per request.
- If the balance drops below the cost of one request, the key automatically falls back to the free tier (requests are not blocked).
- Expired or revoked keys are quietly downgraded to free as well — requests keep going through.
You can manage keys and credits, and review the last 90 days of usage, in the dashboard.