Skip to content

Who actually answered your request?

Hopscotch is one OpenAI-compatible API for every model. Every response names the model, the host that served it and any retries, so a slow or failed call can be traced.

Get an API key

No markup or fees

kimi k3 · 28 Sep 2026[RECORDED]
prompt

Five short questions, each with one right answer.

streamed answer
1. 391
2. Au
3. 1969
4. Canberra
5. 8
[RETURNED BY THE API]
response headers
x-hopscotch-served-by
moonshot-kimi/kimi-k3
x-hopscotch-provider
moonshot
x-hopscotch-retry-attempt-count
0
x-hopscotch-served-via
not sent
x-hopscotch-request-id
be49f694-7f2c-4c33-a098-6b6bccb29813
:x-hopscotch-usage line, before data: [DONE]
prompt_tokens
174
completion_tokens
94
reasoning_tokens
56
provider_elapsed_ms
4,497
[MEASURED BY OUR TEST]
from London, not on the response
first token
3.89 s
last byte
5.46 s
outside the provider
0.96 s

What is Hopscotch?

One API for every model. It speaks the OpenAI format, so you keep the SDK you already use and change two values: the base URL and the key.

OpenAI-compatible
Chat completions, responses and the model list, streamed or not.
500+ models, one key
Every major lab, paid from one prepaid balance.
A receipt on every call
Each response names the model and the host that served it.
No markup or fees
Top up from $10 and all of it is spendable. Each call costs the provider's list price.
two values changepython
import os
from openai import OpenAI

client = OpenAI(
    base_url="https://api.hopscotchlabs.ai/v1",
    api_key=os.environ["HOPSCOTCH_API_KEY"],
)
# everything after this stays as it was
base urlhttps://api.hopscotchlabs.ai/v1

Returned by the API, or measured by us.

Headers and the usage line are on every response you get. The times are what our test worked out from its own clock, and you'd measure them the same way from yours.

[RETURNED BY THE API]
x-hopscotch-served-by
The model that answered, as the host names it, so you can check it is the one you asked for.
x-hopscotch-provider
The host that served the call.
x-hopscotch-retry-attempt-count
How many extra upstream attempts the call took before it was served.
x-hopscotch-served-via
Sent only when a backup route served the call, as backup. An ordinary call doesn't carry it.
x-hopscotch-request-id
The call's id on Hopscotch, on every response, including errors. Quote it when you report a call.
provider_elapsed_ms
How long the host took, timed by Hopscotch, on the usage line at the end of the stream.
[MEASURED BY OUR TEST]
first token
From the moment the request left London to the first streamed text.
last byte
From the request leaving London to the last byte of the stream: the network both ways, Hopscotch and the host, all together.
outside the provider
Last byte minus provider_elapsed_ms: the network plus Hopscotch. It is a ceiling on what Hopscotch added, not a measure of it.

Debugging a slow call.

At 04:45 UTC on 27 Sep 2026, a 24-token DeepSeek V4 Flash answer took 32.12 s. This is what the response said about it.

returned by the api[RECORDED]
x-hopscotch-served-by
deepinfra/DeepSeek-V4-Flash
x-hopscotch-provider
deepinfra
x-hopscotch-retry-attempt-count
0
provider_elapsed_ms
31,462
measured by our test[OUR CLOCK]
first token
32.03 s
last byte
32.12 s
outside the provider
0.66 s

x-hopscotch-request-id 23d394f8-823f-42a2-8d0a-bc0eb7787d61

  1. 01

    Was it the host or Hopscotch?

    provider_elapsed_ms says the host took 31,462 ms. Everything outside it came to 0.66 s, network included.

  2. 02

    Did it retry?

    retry-attempt-count is 0, so the first attempt answered. The time wasn't spent on failed tries.

  3. 03

    Is the host slow, or was it one call?

    The same model five minutes before and after took 2.00 s and 2.00 s, and the other hosts in the same run took 3.9 to 5.8 s. One stall on one call.

  4. 04

    What next?

    Once is worth noting, not acting on. If it keeps happening, build a route that sends this model to another host first, and quote the request id when you report it.

Read it in code.

The OpenAI SDK hides headers by default. Ask for the raw response and they are on it, before the first token of a stream.

The usage line is a server-sent-events comment, so the SDK skips it. To see provider_elapsed_ms, read the raw stream, the way the curl call does.

headers on a streampython
import os
from openai import OpenAI

client = OpenAI(
    base_url="https://api.hopscotchlabs.ai/v1",
    api_key=os.environ["HOPSCOTCH_API_KEY"],
)

with client.chat.completions.with_streaming_response.create(
    model="moonshot-kimi/kimi-k3",
    messages=[{"role": "user", "content": "What is 17 x 23?"}],
    stream=True,
) as response:
    # headers arrive before the first token
    for name in ("request-id", "served-by", "provider",
                 "retry-attempt-count", "served-via"):
        print(name, response.headers.get(f"x-hopscotch-{name}"))

    for chunk in response.parse():
        if chunk.choices and chunk.choices[0].delta.content:
            print(chunk.choices[0].delta.content, end="")
headers and the usage linecurl
curl -sN https://api.hopscotchlabs.ai/v1/chat/completions \
  -H "Authorization: Bearer $HOPSCOTCH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "moonshot-kimi/kimi-k3", "stream": true,
       "messages": [{"role": "user", "content": "What is 17 x 23?"}]}' \
  -D - | grep -i x-hopscotch

What comes back when a call goes wrong.

Streamed Hopscotch calls, sorted by how they ended. Headers arrive before the first token, so a stream cut halfway still has them. The usage line comes at the end, so it doesn't.

fields by how the call ended27 and 28 Sep 2026
field
served2,160
cut27
refused5
request-id
sent
sent
sent
served-by
sent
sent
–
provider
sent
sent
4 of 5
retry-attempt-count
sent
sent
4 of 5
usage line
sent
–
–
provider_elapsed_ms
sent
–
–
error body
–
last data: line
sent

Header names are shown without their x-hopscotch- prefix.

served by a backup route[ILLUSTRATION]
x-hopscotch-provider
backup host
x-hopscotch-served-by
its model id
x-hopscotch-retry-attempt-count
1
x-hopscotch-served-via
backup

Not a recording. No call since 22 Sep has needed a retry or a backup route, so this is what the docs say one carries.

Served and refused calls are 27 and 28 Sep 2026. Cut streams are every one the long-output test has recorded, because a short prompt never runs long enough to be cut. On a cut stream, the error is the last data: line and has no request id in it, so read the id from the header.

You're not the only one.

“If you just click through the onboarding and select a model from the dropdown in ST, you will not know who your provider is and you might be connected to a sub-grade one.”
r/SillyTavernAI
“The cost is a hop that can fail at 3am and swallow the real error.”
r/AgentsOfAI
“what happens on provider timeout. retry, fail over, or surface the error. all three are defensible, silently doing one of them is not.”
r/LLMDevs
“Openrouter / Kimi 2.6 - its just slow. Is this bcos openrouter keeps routing my requets to different providers ?”
r/kimi

Where this stops.

A receipt tells you what happened. It doesn't make a call faster or cheaper on its own.

Who it matters to
[FIT]
Teams that debug slow or failed calls, or audit what they spend. If you only need the answer back, the receipt changes nothing for you.
No retries to show
[0 SINCE 22 SEP]
No call has needed an extra attempt or a backup route since the watcher began, so the count has said 0 every time. It is on the response either way.

How we recorded it.

The watcher runs in public and keeps the full receipt for every call, so you can check each line on this page.

Prompt
Five short questions, each with one right answer. Streamed to five models every 5 minutes from a Cloudflare Worker in London.
Receipt
The watcher keeps the headers and the usage line of every response, and times the stream on its own clock.
Window
The fields table is 27 and 28 Sep 2026: 2,160 served calls and 5 refused. The recorded call (15:40 UTC on 28 Sep 2026) and the slow one are single rows from it.
Comparison
The same prompt runs through another gateway at the same moment. Every result from 23 and 24 Sep 2026 is in the benchmark report.

How to start.

Four steps, and the last one is two lines of code.

01

Create an account

Sign up and verify your email.

02

Add credit

Credit is prepaid. Buy it on the Billing screen, and each call deducts the provider's list price, with no markup or fees.

03

Create a key

Mint one on the Keys screen. It is shown once, so copy it.

04

Change your base URL

Point your OpenAI client at api.hopscotchlabs.ai/v1 with the new key.

See what served every call.

Make an account, point your base URL at Hopscotch, and every response comes back with the model, the host and the retries on it.

No markup or fees