API reference
Content moderation
Endpoints, request fields and response schemas for calling NeonAPI.
POST /v1/moderations
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 |
|---|---|---|---|---|
input | string / string[] | Yes | — | Input in the format required by this endpoint. |
model | string | No | — | Exact published model ID. |
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/moderations \
-H "Authorization: Bearer $NEON_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"input": "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. |
model | string | No | — | Exact published model ID. |
results | object[] | No | — | — |
Download the user API OpenAPI specification
See errors and streaming & tasks.