Headers & observability

Every response carries two headers you should log on the client side. They let you (and us) find any request end-to-end.

X-Request-Id

A stable identifier for the request as it passed through the gateway. If your client already sent one, we propagate it; otherwise we generate it and echo it back.

$ curl -i https://mingo.mingles.ai/v1/chat/completions ...
HTTP/1.1 200 OK
X-Request-Id: req_01HW4QK1V3A5B7C9D
X-Devshard-ID: shard-eu-3

X-Devshard-ID

Identifies which upstream node served your request. Useful when reporting issues or correlating latency by region.

Sending your own request ID

If you have an internal trace ID, just include it on the request:

curl https://mingo.mingles.ai/v1/chat/completions \
  -H "Authorization: Bearer $MINGO_API_KEY" \
  -H "X-Request-Id: my-trace-abc123" \
  ...

We will use it verbatim in our logs and echo it back on the response.

Finding a request

Email us the X-Request-Id (or paste it into the console search box at /app/usage) and we can pull the exact upstream payload, model choice, and latency breakdown.