Find calls in Requests

Requests lists your project's calls, newest first. Open it from the console's sidebar.

Mubit passes each call on and returns the reply. It records the request and reply by default, and Requests shows what served each call.

Filter the list

The row above the list holds the filters:

• the range: Last 24 hours, Last 7 days or Last 30 days;
• Task: All tasks, or one of your tasks by name;
• Served by: who answered each call; Anyone lists them all;
• Errors only: the calls that got a status of 400 or above;
• Session: type a session ID and press Enter to list that session's calls;
• Clear: turns off every filter but the range.

The filters live in the page's address, so a reload or a shared link keeps them.

Errors only reads the calls already loaded, and the line under the filters says how many of them failed. Select Load more to read further.

The chart above the list counts the range's Calls, Errors or Response time. It follows the range and the task only; the other filters narrow the list.

The list

Each row is one call, with its Time, Task, Model asked, Served by, Response time, Status and Rating. A call that no task holds yet shows — under Task.

Load more, under the list, reads older calls.

Read a call's details

Select a row. The call opens in a panel on the right. Its head is the task's name, or Request while no task holds it, with the call's time and the model asked. The panel shows:

• Status: the HTTP status and what it was, such as 200 · answered or 400 · provider error;
• Response: the call's time from start to end;
• Tokens: the tokens in and out;
• Request: the last user message of the call;
• Reply: the answer's text;
• Where the time went: how the call's time divides between Mubit and the model that answered;
• Rate this reply: Good or Bad;
• Details: the call's Request and Session IDs, each with a copy button.

Open as a page opens the call on a page of its own. Close or Escape closes the panel.

A call's session

Details shows the call's Session. Requests in this session, on the call's page, lists the calls that share it. You can also type the session ID in the Session filter.

Tasks and sessions shows how Mubit gives each call a session, and how to name one yourself.

Find a call's request ID

Every answer from Mubit carries the call's request ID in the x-middleware-request-id header: a success, a stream, your provider's error, and Mubit's own error. Mubit's own errors also carry it in their body. It starts with mreq_. Quote it when you ask for help with a call.

To read it:

raw = client.chat.completions.with_raw_response.create(
    model="gpt-6-luna",
    messages=[{"role": "user", "content": "Reply with the word ok."}],
)
print("request id:", raw.headers.get("x-middleware-request-id"))
response = raw.parse()

The Python and TypeScript examples use the client from Connect OpenAI. In curl, -i prints the answer's headers. The header works the same way on Anthropic, Gemini and the OpenAI-compatible services.

Why a call isn't listed

• You just sent it. Reload Requests.
• It's older than the range. Choose a longer range.
• Mubit refused it before calling your provider. A call refused for its key, its path or a missing provider key leaves no record. Look up its code in Troubleshooting.
• It sent x-middleware-store: false, or x-middleware-record set to metadata or off. Mubit keeps no request or answer for such a call, and never lists it.
• It asked for a list of models. Model lists don't show on Requests.