exa_answer
Pack: exa · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/exa_answer for the schema, then POST the same URL with its arguments for the data.
Cited answer to a question: Exa searches the web and writes an answer with the sources it used. Returns the answer, a citations array (title, URL, published date) and the upstream cost. Example: exa_answer({ query: “What is the current federal funds target range?” })
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
query | string | yes | The question or instruction to answer. |
text | boolean | no | If true, include the full page text on each citation. Default false. |
model | string | no | Answer model. Default ‘exa’. |
system_prompt | string | no | Optional extra instructions guiding the answer. |
output_schema | object | no | Optional JSON Schema (Draft 7); the answer is then a structured object matching it. |
Example call
Arguments
{
"query": "What is the current federal funds target range?"
}
curl
curl -X POST https://gateway.pipeworx.io/exa/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"exa_answer","arguments":{"query":"What is the current federal funds target range?"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('exa_answer', {
"query": "What is the current federal funds target range?"
});
Response shape
Always returns: answer, citations
| Field | Type | Description |
|---|---|---|
answer | unknown | The answer: a string, or an object matching output_schema |
citations | array | Sources used for the answer |
costDollars | object | Upstream cost breakdown in USD as reported by the vendor |
Full JSON Schema
{
"type": "object",
"properties": {
"answer": {
"description": "The answer: a string, or an object matching output_schema"
},
"citations": {
"type": "array",
"description": "Sources used for the answer",
"items": {
"type": "object",
"properties": {
"title": {
"type": "string",
"description": "Source title"
},
"url": {
"type": "string",
"description": "Source URL"
},
"publishedDate": {
"type": "string",
"description": "Published date, when known"
},
"author": {
"type": "string",
"description": "Author, when known"
},
"text": {
"type": "string",
"description": "Page text, when text is set"
}
},
"required": [
"url"
]
}
},
"costDollars": {
"type": "object",
"description": "Upstream cost breakdown in USD as reported by the vendor"
}
},
"required": [
"answer",
"citations"
]
}
Connect
Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:
{
"mcpServers": {
"pipeworx": {
"url": "https://pipeworx.io/mcp"
}
}
}
Connect to just the exa pack
{
"mcpServers": {
"exa": {
"url": "https://gateway.pipeworx.io/exa/mcp"
}
}
}
See Getting Started for client-specific install steps.