v0.4 · public beta — keys are issued by hand while we watch how the API gets used

§  Contact

Tell us what your Arabic text does to your pipeline.

API keys, self-hosted licensing, academic access, or a string that comes out wrong — all of it lands in the same inbox, and a person who works on the models reads it.

Self-hosted
Deployment review, licence terms and container access — start with the form and pick “Self-hosted licensing”.
Academic
Reduced rates for university NLP groups and non-profit archives. Tell us the corpus and the paper.
Security
Report anything sensitive to hello@harfscript.com with “security” in the subject; we reply before we fix.
Bad output
Paste the exact string and the request id from x-harf-request-id. That pair is usually enough to reproduce it.
What happens next: we reply within one business day, usually with a key and a quickstart link. Self-hosted enquiries get a short call first — we would rather understand the deployment than send a quote.
POST /contact · harfscript.com accepting requests

optional

No newsletter, no CRM sequence. We use your address to answer you and nothing else. Prefer plain email? hello@harfscript.com

202 ACCEPTED

Message queued.

Thanks — that landed. We reply within one business day, from a real address you can reply to. If it is urgent, mail hello@harfscript.com directly.