NeonAPI Docs
API reference

Legacy text completions

Endpoints, request fields and response schemas for calling NeonAPI.

POST /v1/completions

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

FieldTypeRequiredConstraintsMeaning
modelstringYes—Exact published model ID.
promptstring / string[]Yes—Instruction or generation prompt.
max_tokensintegerNo—Output token limit; model-dependent.
temperaturenumberNo—Sampling temperature where supported.
top_pnumberNo—Nucleus sampling probability.
nintegerNo—Number of generated results; model limits apply.
streambooleanNo—Request incremental streaming events.
stopstring / string[]No——
suffixstringNo——
echobooleanNo——

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/completions \
  -H "Authorization: Bearer $NEON_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "model": "YOUR_MODEL_ID",
  "prompt": "A quiet constellation above a midnight observatory"
}'

Responses

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

StatusMeaning
200Successful response

Response schema

FieldTypeRequiredConstraintsMeaning
idstringNo—Identifier returned for this result or task.
objectstringNo——
createdintegerNo——
modelstringNo—Exact published model ID.
choicesobject[]No—Generated completion candidates.
usageUsageNo—Usage reported by the selected protocol.

Download the user API OpenAPI specification

See errors and streaming & tasks.