API Core
API Explorer Guide
Use the built-in playground to validate payloads, inspect SSE streams, and generate implementation snippets.
7 minUpdated 2026-02-15
Summary
Use the built-in playground to validate payloads, inspect SSE streams, and generate implementation snippets.
4 deep-dive sections0 code samples
Quick Start
- Copy the request sample from this page.
- Run it in API Explorer with your key.
- Confirm stream done payload (finish_reason + charged credits).
- Move the same payload into your backend code.
Why API Explorer exists
API Explorer is the fastest way to validate payload structure and endpoint behavior before coding SDK integration.
- Mode-specific payload templates
- Live request execution with your API key
- Stream event inspector (delta chunks,
route/chunk/trace,done, terminal errors) - Raw and parsed output panes
- Product-scoped assistant for endpoint-specific snippet generation
Typical debugging sequence
Prompt -> payload -> stream -> code
Prepare
- Paste API key
- Choose mode
- Edit JSON payload
Execute
- Run request
- Watch stream events
- Inspect done payload
Integrate
- Generate snippet
- Copy to backend
- Retest with production prompt
Assistant scope
Deliberate scope boundary
The assistant is intentionally limited to LLMWise product and API usage questions. This prevents vague or off-topic answers and keeps examples aligned with real platform behavior.
Good assistant prompts
- "Generate Node.js fetch example with retries for this payload."
- "Show Python SSE parser for done events and finish_reason handling."
- "Explain why this request returned 402 and what user action fixes it."
Docs Assistant
ChatKit-style guided help
Product-scoped assistant for LLMWise docs and API usage. It does not answer unrelated topics.
Sign in to ask implementation questions and get runnable snippets.
Sign in to use assistantPrevious
Compare / Blend / Judge API Reference
Next
Mesh Mode Tutorial (Failover Routing)