For the complete documentation index, see llms.txt. This page is also available as Markdown.

Responses API

Use the OpenAI Responses API for multi-turn, agentic workflows with built-in tool calling.

The Responses API uses the standard Parasail gateway. Use the base URL below with your existing Parasail API key.

Base URL

https://api.parasail.io/v1

Use your existing Parasail API key for authentication. The API key is the same as for all other Parasail endpoints.

Requirements

Requirement
Details

Base URL

https://api.parasail.io/v1

store parameter

Must be set to false on every request. The gateway does not support server-side state storage. Omitting this will return an error.

Authentication

Authorization: Bearer <PARASAIL_API_KEY> (same key as the standard API)

Compatibility

The table below shows which Responses API features are supported.

Feature
Supported
Notes

Single-turn completions

Multi-turn conversations

Pass full conversation history in input

Reasoning / thinking

Reasoning content returned automatically for reasoning models

Function / tool calling

Define tools with tools parameter

Parallel tool calls

Model may issue multiple tool calls in one turn

tool_choice (auto, required, none)

store: true (server-side state)

Must set store: false

previous_response_id (stateful chaining)

Not supported—pass full history in input instead

Streaming

Use stream: true

Web search tool

Not currently available

File search tool

Not currently available

Computer use tool

Not currently available

Quick Start

Python (OpenAI SDK)

cURL

Multi-Turn Conversations

Since previous_response_id is not supported, you maintain conversation history by passing the full message array in input. Each turn appends the assistant's reply and the next user message.

Function Calling (Agentic)

The Responses API supports tool definitions and multi-step agentic loops where the model calls functions and you return results.

Define Tools

Agentic Loop

The model may call multiple tools in parallel within a single turn. Always provide results for every function_call before sending the next request.

Important Notes

  • Always set store: false. Every request must include "store": false. Server-side response storage is not supported, and omitting this parameter will result in an error.

  • No stateful chaining. The previous_response_id field is not supported. Manage conversation history client-side by passing the full input array each turn.

  • Same API key. Your existing Parasail API key works across all endpoints. No separate key is needed.

  • Model-specific controls. For DeepSeek, Qwen3.5, and GPT-OSS thinking and reasoning parameters, see model-specific notes.

  • Model availability. Not all models are available for the Responses API. Use the /v1/models endpoint to check:

Last updated