QuickSilver API
Last updated
Welcome to the QuickSilver API! This guide will help you quickly set up your API key and choose the best integration method for your needs.
QuickSilver API is fully compatible with OpenAI’s Chat Completions API.
If you’re already using OpenAI’s API, you can switch to QuickSilver with minimal or no changes to your existing integration.
Before you can use the Quicksilver API, you must create and manage your API key.
👉 View API Key Setup
Your API key is required for all requests and should be included in the Authorization header:
Authorization: Bearer your-api-keyKeep this key secure and never expose it publicly.
QuickSilver supports multiple integration paths to suit your environment:
Use the OpenAI-compatible Python client
Ideal for browser-based or Node.js applications
Direct HTTP requests using tools like curl
Test and automate with our command-line tool
Integrate via Model Context Protocol clients
Add a chat widget directly to your website
Use QuickSilver in the desktop client
Use this to send chat messages and receive assistant replies (OpenAI-compatible).
Use this endpoint for streaming responses in real time.
The API returns standard HTTP status codes and JSON-formatted errors (compatible with OpenAI’s error structure).
Example error response:
The API is fully compatible with OpenAI’s Chat Completions interface
Secure your API key — never share it publicly
For multi-turn conversations, pass previous messages in the messages array
Use the SSE endpoint for streaming responses in real time
All communication is encrypted via HTTPS
Contact Support – Reach out for technical assistance
Refer to OpenAI client documentation for help with SDK usage
Last updated
https://api-quicksilver.iotex.ai/v1POST /chat/completionsGET /sse?authorization=your-api-key{
"error": {
"message": "Invalid API key provided",
"type": "invalid_request_error",
"code": "invalid_api_key"
}
}