Skip to main content
POST
/
v3
/
exa
/
answer
Exa Answer
curl --request POST \
  --url https://api.novita.ai/v3/exa/answer \
  --header 'Authorization: <authorization>' \
  --header 'Content-Type: <content-type>' \
  --data '
{
  "query": "<string>",
  "text": true,
  "outputSchema": {},
  "type": "<string>",
  "properties": {},
  "required": [
    "<string>"
  ],
  "items": {},
  "additionalProperties": {}
}
'
{
  "400": {},
  "401": {},
  "403": {},
  "404": {},
  "429": {},
  "500": {},
  "502": {},
  "503": {},
  "requestId": "<string>",
  "answer": {},
  "citations": [
    {}
  ],
  "title": "<string>",
  "url": "<string>",
  "publishedDate": "<string>",
  "author": "<string>",
  "id": "<string>",
  "image": "<string>",
  "favicon": "<string>",
  "text": "<string>"
}
This document describes the Exa passthrough endpoints exposed by the platform gateway. It is based on Exa’s Search, Get Contents, and Answer APIs, with platform route prefixes applied. Base URL example: https://api.novita.ai Generate an answer to a question using Exa search results, with optional citations and source text.

​
Request Headers

All endpoints require platform API authentication.
​
Content-Type
string
required
Use application/json.
​
Authorization
string
required
Platform API key, formatted as Bearer <api_key>.

​
Request Body

​
query
string
required
Natural-language question or instruction. Minimum length is 1.
​
text
boolean
Whether to return source page text. Default is false.
​
outputSchema
object
JSON Schema Draft 7 object for structured answer output. See Answer Output Schema.

​
Answer Output Schema

outputSchema accepts a JSON Schema object for structured answer output.
​
type
string
JSON Schema root type, commonly object.
​
properties
object
Field definitions for the structured answer.
​
required
string[]
Required property names.
​
items
object
Array item schema when a property is an array.
​
additionalProperties
boolean | object
Whether undeclared fields are allowed, or a schema for additional fields.

​
Request Example

curl -X POST 'https://api.novita.ai/v3/exa/answer' \
  -H 'Authorization: Bearer <api_key>' \
  -H 'Content-Type: application/json' \
  -d '{
    "query": "What is the latest valuation of SpaceX?",
    "text": true
  }'

​
Structured Answer Example

curl -X POST 'https://api.novita.ai/v3/exa/answer' \
  -H 'Authorization: Bearer <api_key>' \
  -H 'Content-Type: application/json' \
  -d '{
    "query": "Compare three recent AI infrastructure funding rounds.",
    "outputSchema": {
      "type": "object",
      "properties": {
        "companies": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "name": {"type": "string"},
              "round": {"type": "string"},
              "amount": {"type": "string"}
            },
            "required": ["name", "round", "amount"]
          }
        }
      },
      "required": ["companies"]
    }
  }'

​
Response

​
requestId
string
Unique request identifier.
​
answer
string | object
Generated answer. It can be structured according to Answer Output Schema.
​
citations
object[]
Search results used to generate the answer.

​
Citation Object

​
title
string
Source title.
​
url
string
Source URL.
​
publishedDate
string
Published date when available.
​
author
string
Author when available.
​
id
string
Exa document ID.
​
image
string
Associated image URL.
​
favicon
string
Site favicon URL.
​
text
string
Source text when requested.

​
Errors

The platform may return standard HTTP errors before forwarding the request, and Exa may return upstream errors after forwarding.
​
400
status
Invalid request body or unsupported parameter value.
​
401
status
Missing or invalid API key.
​
403
status
Access denied by platform or upstream provider.
​
404
status
Route or requested resource not found.
​
429
status
Rate limit exceeded.
​
500
status
Internal server error.
​
502
status
Upstream provider error.
​
503
status
Service unavailable.

​
Notes

  • All request bodies are JSON.
  • Extra Exa parameters not listed here may be passed through.
  • Response shapes can vary depending on request options.
  • This document intentionally omits billing-related fields.

​
References

For more details, see the Exa Answer API reference.
Last modified on June 12, 2026