exa-deploy-integration

name	exa-deploy-integration
description	Deploy Exa integrations to Vercel, Docker, and Cloud Run platforms. Use when deploying Exa-powered applications to production, configuring platform-specific secrets, or building search API endpoints. Trigger with phrases like "deploy exa", "exa Vercel", "exa production deploy", "exa Cloud Run", "exa Docker".
allowed-tools	Read, Write, Edit, Bash(vercel:*), Bash(fly:*), Bash(gcloud:*), Bash(docker:*)
version	1.11.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","exa","deployment","vercel","docker"]
compatibility	Designed for Claude Code, also compatible with Codex and OpenClaw

Exa Deploy Integration

Overview

Deploy applications using Exa's neural search API to production. Covers API endpoint creation, secret management per platform, caching for production traffic, and health check endpoints.

Prerequisites

• Exa API key stored in EXA_API_KEY environment variable
• Application using exa-js SDK
• Platform CLI installed (vercel, docker, or gcloud)

Instructions

Step 1: Vercel Edge Function

// api/search.ts — Vercel API route
import Exa from "exa-js";

export const config = { runtime: "edge" };

export default async function handler(req: Request) {
  if (req.method !== "POST") {
    return new Response("Method not allowed", { status: 405 });
  }

  const exa = new Exa(process.env.EXA_API_KEY!);
  const { query, numResults = 5 } = await req.json();

  if (!query || typeof query !== "string") {
    return Response.json({ error:  }, { :  });
  }

   {
     results =  exa.(query, {
      : ,
      : .(numResults, ),
      : { :  },
      : { : , query },
    });

     .({
      : results..( ({
        : r.,
        : r.,
        : r.,
        : r.?.(, ),
        : r.,
      })),
    });
  }  (: ) {
     status = err. || ;
     .(
      { : err., : err. },
      { status }
    );
  }
}