---
title: "Check whether the caller may see the in-product Aletheia assistant (DARK MVP)."
method: GET
path: "/aletheia/gate"
tags: ["Aletheia Support"]
---

# Check whether the caller may see the in-product Aletheia assistant (DARK MVP).

`GET /aletheia/gate`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/aletheia/gate`
- Auth: none required

The single check the front-of-house widget polls BEFORE rendering (MNE-1930/1931) — the backend is the ONLY authority; the client never inspects the flag or allowlist itself. Reuses the exact `supportAccessAllowed` predicate `POST /v1/aletheia-support/{chat,voice}` enforce, so this can never drift out of sync with what those routes would actually allow. Unlike the chat/voice routes, ALWAYS returns 200 — the gate-check's own existence isn't sensitive (it reveals nothing about grounding/answers) — with `allowed` reflecting the real decision (`false` for flag-off, non-allowlisted, or no caller at all).

## Response `200`

Always returned, for every caller.

- object
  - `allowed` boolean, required

## Other responses

- `429`: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
- `500`: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.

---

[API](https://skmtc.dev/mnemom/apis/mnemom-api.md) · [All operations](https://skmtc.dev/mnemom/apis/mnemom-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mnemom/apis/mnemom-api/revisions/274b7a6ea182?raw)