Exa Airtable

Latest Audit Result

Audited exa-airtable at commit 67fb3fb against current docs.exa.ai and the April 1, 2026 deprecation changelog. It is a direct REST integration with no Exa SDK dependency. Active /search usage is current (type: deep, outputSchema, contents.highlights.maxCharacters, x-exa-integration: airtable), and no sunset/deprecated API features are used. However, /answer is declared but only present in unreachable UI code and sends an invalid type parameter; the monitors code is also unreachable and uses outdated /search-monitors paths plus an unsupported cron trigger shape. Full report: https://kitchen-sink.exa.ai/content-host/view/exa-airtable-api-audit-795ea11e

Missing Features (11)

• Declared endpoint 'answer' is not implemented in the accessible UI: GenerateReport exists but ExaApp only renders CreateWebTable.
• Declared content option 'text' is not implemented in the active accessible search flow: /search requests contents.highlights, and the only text request is in unreachable monitor code.
• Monitors feature code is not currently functional against the public API: it uses /search-monitors instead of /monitors.
• Monitors feature code uses an unsupported cron trigger payload; current public API supports interval triggers only.
• /answer feature code sends an invalid type: 'deep' request parameter.
• No DEPRECATED feature usage found: the integration does not use /research, resolvedSearchType, highlightScores, startCrawlDate, endCrawlDate, numSentences, highlightsPerUrl, useAutoprompt, or context.
• Migrate monitor calls from /search-monitors to /monitors for create, trigger, list runs, get run, and delete operations.
• Replace monitor trigger payloads from { type: 'cron', expression, timezone } to the current interval trigger shape { type: 'interval', period: '1d' } or omit trigger for manual-only monitors.
• Remove type: 'deep' from /answer requests; current /answer docs accept query, stream, text, and outputSchema, not a search type parameter.
• Wire NewsMonitor and GenerateReport into ExaApp, or remove them from declared capabilities if they are not intended to be user-accessible.
• Implement the declared text content option in an accessible flow; the active /search flow currently requests highlights, while text appears only in unreachable monitor code.