Billing / Over-limit behavior

Silent Mode Explained

By default an over-limit request returns HTTP 200 with an empty payload instead of an error. Compare both modes and their exact responses.

Comparison

Compare the two modes

Over-limit write

HTTP 200
{ "status": "ok" }

Over-limit retrieval

HTTP 200
{ "memories": [] }

An AI pipeline keeps working instead of surfacing a billing error to your end user. Nothing is stored and nothing is returned, but the call succeeds.

The risk is not noticing. Watch your usage and configure an alert, because your application will look healthy while memory has quietly stopped.

Client code

Handle it in your client

Because the default response is a successful empty payload, the check that matters is whether content came back — not whether the call failed.

result = ms.query("What are the user's preferences?", k=5)

if not result.memories:
    # Valid outcome: no relevant memory, or the monthly limit was reached.
    # Answer without memory, and let your usage dashboard tell you which.
    prompt = base_prompt
else:
    prompt = base_prompt + render(result.memories)

Was this page helpful?

← Previous

Billing + Quota Flow

Overages & Limits