anoman
Indonesian-Language Chatbot

Indonesian-Language AI Chatbot with Guardrails.

One OpenAI-compatible endpoint for 400+ LLMs — with NIK and phone-number masking before data reaches the LLM, Indonesian-language content moderation, and data stored in Jakarta.

Why chatbots need a gateway

Customer-service chatbots receive the most sensitive data: NIK, phone numbers, addresses, even account numbers — typed freely by users. If those messages are forwarded raw to an overseas LLM API, your users' personal data goes with them. Anoman sits between your app and the LLM provider: every request passes through a guardrails pipeline (prompt injection detection, PII masking, content moderation) before a single token leaves your boundary.

Automatic NIK & phone masking

Our PII scanner detects NIK (KTP), phone numbers, email, and credit cards in every request — then redacts, tokenizes, or blocks them before they reach the LLM provider.

Indonesian-language content moderation

The content moderation filter supports both Indonesian and English — a combination of keywords and ML classification — so your chatbot never forwards harmful content in either language.

Prompt injection detection

Every user message is checked by an ML classifier before it is processed. Jailbreak attempts or hidden instructions are blocked with HTTP 403 — not forwarded to the model.

Data stays in Jakarta

Conversation prompts, responses, and traces are stored in a Jakarta data center — built to help your chatbot app's readiness for UU PDP.

Without changing code

The endpoint is OpenAI-compatible — just change the base URL to https://api.anoman.io/v1 and your chatbot is instantly protected. The OpenAI SDK, LangChain, or any agent framework keeps working as usual.

curl https://api.anoman.io/v1/chat/completions \
  -H "Authorization: Bearer anm-sk-..." \
  -d '{
    "model": "gpt-4o-mini",
    "messages": [{
      "role": "user",
      "content": "Please check my order status. NIK 3201234567890001, phone 0812-3456-7890"
    }]
  }'
Four PII handling modes
  • Redact — replace with a placeholder such as <ID_NIK>
  • Tokenize — reversible tokens; the original value is restored in the final response
  • Synthetic — realistic fake values so the model keeps full context
  • Block — reject the request when a sensitive entity is present
Jakarta data residency

Conversation prompts, responses, and logs are stored in Indonesia — your chatbot users' data stays in Jakarta.

UU PDP-readyJakarta

Start free with a daily guarded allowance plus a premium-model trial credit, or see the tier pricing comparison. Related: UU PDP readiness for AI apps and cut LLM costs.

Frequently asked questions

Do I need to change my chatbot code to use Anoman?

No. Anoman's endpoint is OpenAI-compatible — just point the base URL to https://api.anoman.io/v1 and your chatbot is instantly protected. The OpenAI SDK, LangChain, or any agent framework keeps working as usual, with access to 400+ LLMs through a single endpoint.

How does Anoman protect chatbot users' personal data?

Our PII scanner detects NIK (KTP), phone numbers, email, and credit cards in every request, then redacts, tokenizes, replaces them with synthetic values, or blocks them before the data reaches the LLM provider. The X-Anoman-Guardrail-Pii response header confirms which entities were masked.

Does the content moderation support Indonesian?

Yes. Anoman's content moderation filter works in both Indonesian and English — a combination of keywords and ML classification. In the same pipeline, an ML classifier checks every message for prompt injection and blocks jailbreak attempts with HTTP 403.

Build a chatbot that's safe for Indonesian users.