Browserbase

Latest Audit Result

Browserbase is a docs-only integration page that links to Browserbase-hosted TypeScript/Python templates. The Exa docs page itself has no inline code examples and the declared capabilities (search, get_contents; auto; text/highlights) are conceptually covered, but the linked template examples are outdated against current Exa API/docs patterns.

Missing Features (7)

• DEPRECATED: Linked Browserbase templates use the deprecated Exa `context` option (`context: true` / `context=True`) during careers-page search; current docs say to use `highlights` or `text` instead.
• Linked Browserbase templates use outdated `livecrawl` request parameters (`livecrawl: "fallback"` / `livecrawl="fallback"`) instead of current `maxAgeHours` freshness guidance.
• Linked Browserbase templates call older `searchAndContents` / `search_and_contents` SDK helpers with top-level `text: true`; current Exa docs recommend `search(...)` with nested `contents` options on `/search`.
• Update the linked TypeScript and Python template examples from `searchAndContents`/`search_and_contents` with top-level `text: true` to current `search` calls using nested `contents` options, e.g. `contents: { highlights: true }` or `contents: { text: true }` for JavaScript and `contents={"highlights": True}` or `contents={"text": True}` for Python.
• Replace `livecrawl: "fallback"` / `livecrawl="fallback"` in the linked templates with current freshness guidance: omit freshness controls for default fallback behavior, or use `contents.maxAgeHours`/`max_age_hours` for `/search` plus `livecrawlTimeout` only when explicit freshness is required.
• Replace the careers-page lookup's deprecated `context: true` / `context=True` option with `contents` highlights or text; current SDK docs mark the `context` option/response field as deprecated and recommend `highlights` or `text` on individual results.
• The public Browserbase docs page describes only the workflow and links to external code; it should include or point to a current minimal Exa snippet showing `POST /search` or SDK `search` with `type: "auto"` and nested `contents` to make endpoint/parameter shape clear.