English ↔ written ASL gloss

Meaning, made easier to share.

Lipgloss translates one independent text snippet at a time between English and ASL gloss, while keeping the original text visible beside its translation.

What Lipgloss is

A translation layer for written text

ASL gloss is a written notation used to represent signs and aspects of ASL structure. It is not ASL itself, sign-language video, or a replacement for a fluent interpreter in medical, legal, emergency, or other high-stakes settings.

Two directions

Translate English into ASL gloss or turn ASL gloss into flowing English.

Independent snippets

Each request stands alone. Lipgloss does not treat your next snippet as part of an ongoing conversation.

Meaning first

The service translates the text you provide. It does not answer a question or carry out instructions found inside it.

Translation demo

Translate a real snippet

Choose the direction, enter up to 2,000 characters, and keep the original text alongside the structured result.

Translation input

Required. Your text is treated as an independent snippet, not conversation memory.

Translation result

Enter a snippet to begin.

Developer documentation

Use the translation API

The current interface is the authenticated FlowClick MCP tool lipgloss.translate. It is not an anonymous public REST endpoint, and no credential belongs in browser JavaScript.

Request

Send all three fields. Language codes are eng and asl; input and output must differ.

{
  "text": "I am happy.",
  "inputLanguage": "eng",
  "outputLanguage": "asl"
}

Structured response

A successful response preserves the source in its corresponding field and returns the translation in the other.

{
  "ok": true,
  "englishPrompt": "I am happy.",
  "aslGlossPrompt": "I HAPPY",
  "requestId": "…",
  "promptVersion": "v4",
  "schemaVersion": "lipgloss.translate.v1",
  "direction": "eng_to_asl",
  "modelInvoked": true
}

Validation and errors

Empty text, text over 2,000 Unicode code points, unknown language codes, and same-language requests are rejected before model invocation. Provider and schema failures return ok: false with a stable errorCode and safe message.

Access note: Pilot access is restricted and usage controls are still part of production hardening. Contact hello@lipgloss.io to discuss an integration.

GlossBy

A paired text-message companion in development

GlossBy is designed to relay translated snippets between registered participants, using each person’s explicit language preference. It is not yet open for live SMS enrollment or public messaging.

  1. Register and consent. Both participants confirm the pair and choose explicit source and preferred output languages.
  2. Send one snippet. Each message is handled independently; GlossBy does not guess the language or build conversational memory.
  3. Receive a translation. The system translates to the paired recipient’s preference and tracks delivery state. STOP and suppression take priority.

Pilot status: Signed ingress, duplicate protection, suppression, and delivery behavior must pass controlled testing before live availability is announced.