Content Policy

Content Exa refuses to search for, the errors a refused request returns, and how warnings and revoked API access work.

Exa refuses requests that seek child sexual abuse material or any other content that sexualizes minors. A refused request returns no results.

​

Errors

A refused request returns 403 with one of these tags:

Tag	Meaning
PROHIBITED_CONTENT	The request seeks prohibited content and was refused. Other requests from your team are served.
TEAM_BLOCKED	Your team’s API access has been revoked and every request with its API keys is refused.

{
  "requestId": "67207943fab9832d162b5317f4cca830",
  "error": "A human-readable explanation of the refusal.",
  "tag": "PROHIBITED_CONTENT"
}

Do not retry a refused request. The same request is refused again and counts toward the warnings described below.

​

Warnings and revoked access

Exa reviews refused requests by team. A team whose requests repeatedly seek prohibited content receives a warning, shown to its members at the top of the dashboard. Repeated violations may result in the team’s API access being permanently revoked. A team whose access is revoked has its API keys refused with TEAM_BLOCKED. Its members can still sign in, but see a message that the team’s access has been revoked instead of dashboard pages while using that team; they can switch to another team in good standing.

​

Send userIdentifier for your users

If your product sends requests on behalf of your users, use an opaque userIdentifier that does not contain personal information such as an email address or name. Hash those values before sending them.

​

Contact

If you believe a request was refused in error, or your team was warned or had its API access revoked, contact [e-mail]. Include the requestId of an affected request.