Compact a conversation

POST /v1/responses/compact

Authentication

Use your NeonAPI API key in Authorization: Bearer YOUR_API_KEY. Keep the key in a trusted application environment.

Availability and compatibility

Check the selected model’s protocol, permissions, price and supported parameters before calling. Unsupported parameters may be rejected. Request examples use placeholders.

Request fields

application/json

Field	Type	Required	Constraints	Meaning
`model`	`string`	Yes	—	Exact published model ID.
`input`	`string / object[]`	No	—	Input in the format required by this endpoint.
`instructions`	`string`	No	—	—
`previous_response_id`	`string`	No	—	—

Full field definitions, nested objects and referenced schemas are available in the downloadable specification.

Request example

export NEON_API_KEY="YOUR_API_KEY"
curl https://neon-api.com/v1/responses/compact \
  -H "Authorization: Bearer $NEON_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "model": "YOUR_MODEL_ID",
  "input": [
    {
      "role": "user",
      "content": "Hello"
    }
  ]
}'

Responses

Fields vary by model and protocol. The schema below describes the documented successful response; streams use protocol-specific events.

Status	Meaning
200	Successful response

Response schema

Field	Type	Required	Constraints	Meaning
`id`	`string`	No	—	Identifier returned for this result or task.
`object`	`string`	No	—	—
`created_at`	`integer`	No	—	—
`output`	`object[]`	No	—	Generated response items.
`usage`	`Usage`	No	—	Usage reported by the selected protocol.
`error`	`object`	No	—	—

Download the user API OpenAPI specification

See errors and streaming & tasks.