About Oathbreaker.
A model API for independently minded developers.
Who operates Oathbreaker AI?
Oathbreaker AI is operated by Formacha LLC, a United States company. We provide prepaid access to text models through an OpenAI-compatible Chat Completions API. Developers can connect Hermes and other agents, build their own applications, or try a conversation in the account console.
Our official website is oathbreaker.ai. Our public developer organization is Oathbreaker AI on GitHub. For account, billing, technical support, or abuse reports, email support@oathbreaker.ai.
What does the service provide?
The API supports text chat, streaming responses, and function calling. Your application executes its own tools. Oathbreaker manages API keys, prepaid credit, usage accounting, and the gateway between your application and inference.
See the GLM-5.3 Abliterated model page for the model currently offered, pricing for token rates, and the API reference for supported features and limits. Compatibility refers to the supported Chat Completions format; it does not imply support for every OpenAI API.
Who provides the model inference?
Oathbreaker currently routes model requests to Refuseless for inference. We are the API service operator, not the original developer of the underlying GLM model. The model page distinguishes our public API identifier from the upstream model identifier.
Prompts and responses pass through our hosting and inference providers. Our account database does not save prompt or response text; it records operational information such as token usage, charges, timestamps, and request status. Provider processing and retention have separate terms. The privacy policy explains the full data flow and its limits.
What does “take the oath” mean?
The entrance oath expresses our expectation that people remain responsible for how they use the service. Abliterated models can respond differently from other assistants; the label does not guarantee an answer, accuracy, or a successful task. Review outputs and approve consequential tool actions in your application.
The terms of service set out acceptable use, billing, and account responsibilities. They apply alongside the entrance experience.
Start with a small, inspectable workflow.
Follow the agent setup guide or use the Python and JavaScript examples. Start with a limited output budget, inspect your usage, and increase the scope when the workflow behaves as expected.