# How to use a Righthand with Exa

Use Righthand to prepare an Exa source-discovery review that distinguishes search relevance from evidence supporting a decision.

By Righthand Team · 2026-10-12

Source: https://www.righthand.ai/blog/how-to-use-righthand-with-exa

## Quick answer

Use Righthand to prepare an Exa source-discovery review that distinguishes search relevance from evidence supporting a decision. Keep document dates and exact source URLs.

Start with a reviewable deliverable, keeping Exa as the accepted home for its records. This guide uses an explicitly approved snapshot or browser read; it does not assume that every provider API action is exposed by your Righthand connection.

## Evidence and access

Exa documents search and content-oriented result options. See the [official Exa reference](https://docs.exa.ai/reference/search). Provider capabilities and Righthand's available tools are separate checks.

Use the owner's supplied search or content results with query, URL, retrieval date, content scope, and approved research question. Verify the required tools and owner-approved scope through [Righthand integrations](/integrations); use the supplied packet when a native read is unavailable.

## Define the objects and authority

Include these fields in the working input: query, filters, result URL, title, retrieved content, source date, inclusion reason. These are the requested review columns, not a promise that every provider endpoint returns them under those exact names.

A semantically relevant result can still be outdated or secondary. The reviewer decides which evidence belongs in the final brief.

| Responsibility | Owner |
| --- | --- |
| Prepare source scope and access | Account owner |
| Organize evidence and proposed next steps | Righthand |
| Approve consequential changes | the research lead |

## Illustrative first-run brief

> Use the owner-provided Exa snapshot or approved read-only view. Review the supplied search sample for workflow vendors. Identify primary documentation and duplicate sources. Draft a shortlist of pages to verify without new searches. Run once for the agreed sample, using America/Los_Angeles for the review deadline and preserving source timestamps separately. Return the draft in this conversation by Friday at 3 PM Pacific for the research lead to review. Include source references and missing fields. Do not write records, spend money, change permissions, or send external messages. Stop and report an unavailable source rather than substituting another account.

## Expected result and verification

Two URLs can repeat the same announcement. The shortlist groups them rather than counting them as independent corroboration.

Open a selected source and compare its actual text and date with the extracted result. Record the source cutoff, applied filters, and items excluded from the sample. The reviewer should be able to follow each consequential finding back to an original object. A well-written summary is not evidence that a proposed action happened. If a later write is authorized, verify its specific result separately before changing the task's status.


### Illustrative input and draft output

These synthetic entries show the requested review, not live account results or a provider field schema.

| Source item | Supplied observation | Draft conclusion |
| --- | --- | --- |
| Page A | Organization and fact match | Use bounded claim |
| Page B | Similar name, different company | Exclude association |
| Page C | Conflicting dated version | Ask reviewer to reconcile |

## Common failure and recovery

A missing publication date should remain unknown. Ask for an explicit recency check instead of sorting undated pages as new.

If similar pages refer to different organizations, check source identity and separate them before combining facts in a summary.

## FAQ

### What should the reviewer verify first?

Verify the organization, source URL, date, and exact claim support. A relevant search result is a candidate source rather than a verified conclusion.

### How should a repeat run be scoped?

Preserve query, filter rules, and retrieval timestamps between reviews. Recheck changed pages and keep deduplicated URLs traceable instead of merging conflicting source versions.

For connection and permission details, use [Righthand Docs](https://docs.righthand.ai). Review [Pricing](/pricing) alongside any separate provider charges before expanding the workflow.