Check your HTTP connection and client setup without signing in, funding an account or running a model.
Public simulation key
sk-test-00000000000000000000000000000000Base URL: https://unbound-me.com/v1
Use this exact public key in the API key field instead of a placeholder. It is not a personal credential. Every supported generation request with this key returns a fixed simulation, even if you select a production model ID. For real API usage, replace this test API key with your real Unbound API key.
Try it
curl https://unbound-me.com/v1/chat/completions \
-H 'Authorization: Bearer sk-test-00000000000000000000000000000000' \
-H 'Content-Type: application/json' \
-d '{"model":"unbound-test","messages":[{"role":"user","content":"Test my connection"}]}'The assistant always says:
This request completed successfully. This is the Unbound test API: no model was run and no funds were charged. For real API usage, replace this test API key with your real Unbound API key.
Add "stream":true for a simulated stream. Normal JSON and streaming are available for Chat Completions, legacy text Completions, Responses and Anthropic-compatible Messages. Messages also accepts this key through x-api-key; do not mix test and real credentials.
What is simulated?
- GET /v1/models lists unbound-test and public model IDs for client discovery.
- POST /v1/chat/completions, /v1/completions, /v1/responses and /v1/messages return the same fixed text.
- Reported token usage and charge are zero. Responses carry the X-Unbound-Test: true header and test metadata.
- The simulator does not run inference, read account balances, reserve funds, create usage receipts or grant API credit. Prompts are not echoed or saved.
- This tests transport and response parsing, not model quality, tool execution, embeddings, real request validation or billing. Model, prompt and tool instructions do not control the fixed response.
- Only this exact key activates simulation. Real customer keys continue to use the protected, billable API. This key does not sign you into the website or grant account, key-management, administrator or MCP access.
Fair-use limits
The public simulator accepts JSON bodies up to 16 MiB, 20 requests per minute per IP, 120 requests per minute across the service and 4 concurrent requests. A 429 response means retry later; errors are not billable. These simulation limits do not redefine the limits of a real customer API key.
OpenCode
Follow the OpenCode setup guide, enter the public test key at the key prompt and select an Unbound model. The response is deliberately simulated. Replace the stored test credential with a real Unbound inference key when you want actual model answers.
