API Terms of Service

These API Terms govern programmatic access to InKhmer public APIs — starting with the AI document translator at /v1/public/document-translator. They supplement the general Terms of Service; where the two conflict, these API Terms control for API usage. Using the web UI alone does not bind you to this document.

API access requires a TosKey API key issued through the TosKey Console (S5 → InKhmer). Keys carry scopes — translator:translate, translator:read and translator:cancel — and every request must present a valid key as a Bearer token.

1. Keep keys secret; activity under your key is your responsibility.
2. Rotate keys immediately if they may have leaked, and use sk_test_ keys for development and CI.
3. Do not share keys between organisations or resell raw API access.

API jobs are metered in prepaid credits debited at job creation according to the published per-page pricing table.

1. Debits are idempotent — a repeated Idempotency-Key replays the original response without charging twice.
2. Jobs that fail before completion are automatically refunded to the wallet.
3. Jobs you cancel are refunded for the untranslated pages.
4. Credits are non-transferable and not redeemable for cash; wallet balances follow the general refund policy.

Per-key and per-account rate limits are enforced at the gateway. Responses that exceed a limit return 429 with Retry-After and X-RateLimit-* headers — your client must honor them.

1. Do not rotate through multiple keys to bypass a limit.
2. Burst capacity above the standard limits requires an operator-assigned tier; contact us to request one.
3. Repeated limit violations may lead to temporary key throttling after notice.

You may only submit documents you have the right to process. You must not use the API to:

1. process content that is unlawful, infringing, or violates third-party privacy;
2. probe, scan, or attack the service or its rate limits;
3. misrepresent the origin of requests or spoof identity headers;
4. extract, scrape, or rebuild the translation engine itself.

Uploaded originals are stored for up to 24 hours and translated outputs for up to 7 days, after which the objects are deleted. Job metadata (page counts, pricing tier, status) is retained for billing and abuse review.

1. Document text is never shared with other customers or used in public output.
2. Admin drill-down shows job metadata only — document bodies are not exposed in dashboards.
3. You are responsible for the legality of the documents you submit.

Completed API jobs produce a watermark-free PDF downloadable through the job's /pdf endpoint. You receive a perpetual license to use the translated output for any lawful purpose; we retain no rights over your document content.

The public API is offered on a best-effort basis with no uptime SLA in v1. Breaking changes are published under a new version path with advance notice on the developer portal; non-breaking additions may ship without notice. No webhooks exist in v1 — poll the job endpoint for state.

Abnormal usage — for example sustained high-volume traffic with elevated error rates — triggers an operator review. We may suspend or revoke a key for fraud, abuse, security risk, or breach of these terms, and will notify the account owner when a key is revoked. You may stop using the API at any time; remaining credits follow the refund policy.

To the extent permitted by law, InKhmer's aggregate liability for API claims is capped at the credits you purchased in the 90 days before the claim. The API is provided "as is" without warranties of uninterrupted operation. Questions: info@inkhmer.com.