@wolpertingerlabs/drawlatch 1.0.0-alpha.35 → 1.0.0-alpha.37

package/CONNECTIONS.md

@@ -29,6 +29,7 @@ Connection templates are loaded when a caller's session is established. Custom c
 | `devin`         | [Devin AI API](https://docs.devin.ai/api-reference/overview)                                  | `DEVIN_API_KEY`                            | Bearer token header                   |
 | `discord-bot`   | [Discord Bot API](https://discord.com/developers/docs/intro)                                  | `DISCORD_BOT_TOKEN`                        | Bot token header (see note)           |
 | `discord-oauth` | [Discord OAuth2 API](https://discord.com/developers/docs/topics/oauth2)                       | `DISCORD_OAUTH_TOKEN`                      | Bearer token header (see note)        |
+| `exa`           | [Exa Search API](https://docs.exa.ai/reference/getting-started)                               | `EXA_API_KEY`                              | x-api-key header (see note)           |
 | `github`        | [GitHub REST API](https://docs.github.com/en/rest)                                            | `GITHUB_TOKEN`, `GITHUB_WEBHOOK_SECRET`    | Bearer token header (see note)        |
 | `google`        | [Google APIs](https://developers.google.com/apis-explorer)                                    | `GOOGLE_API_TOKEN`                         | Bearer token header (see note)        |
 | `google-ai`     | [Google AI Gemini API](https://ai.google.dev/api)                                             | `GOOGLE_AI_API_KEY`                        | x-goog-api-key header (see note)      |
@@ -55,6 +56,8 @@ Connection templates are loaded when a caller's session is established. Custom c
 
 > **Discord note:** Discord has two connection types. `discord-bot` uses the `Bot` authorization prefix for bot tokens, which have full access to most API routes (guilds, channels, messages, etc.). `discord-oauth` uses a standard `Bearer` token obtained via OAuth2, which provides user-scoped access limited to the authorized scopes (identity, guilds list, email, etc.). Both target the same v10 API base URL.
 
+> **Exa note:** The Exa Search API uses a custom `x-api-key` header instead of the standard `Authorization: Bearer` pattern. All endpoints are POST requests to `https://api.exa.ai` with a JSON body — the main ones are `/search` (neural or keyword web search), `/contents` (fetch cleaned page text, highlights, and summaries), `/findSimilar` (semantically similar pages), and `/answer` (a sourced answer to a question). Create an API key in the [Exa Dashboard](https://dashboard.exa.ai/api-keys).
+
 > **Google AI note:** The Google AI (Gemini) API uses a custom `x-goog-api-key` header instead of the standard `Authorization: Bearer` pattern. This is separate from the `google` connection — use `google` for Workspace APIs (Sheets, Drive, etc.) and `google-ai` for Gemini LLM endpoints. The endpoint is not version-pinned (`generativelanguage.googleapis.com/**`) to allow access to both `v1` and `v1beta` paths.
 
 > **Google APIs note:** Google Workspace APIs span many subdomains (sheets.googleapis.com, drive.googleapis.com, etc.). The `google` connection allowlists the most common domains. If you need additional subdomains, add a custom route with the same `GOOGLE_API_TOKEN` secret. For Google AI / Gemini, use the `google-ai` connection instead.

package/dist/connections/ai/exa.json

@@ -0,0 +1,24 @@
+{
+  "name": "Exa Search API",
+  "stability": "beta",
+  "category": "ai",
+  "description": "Exa AI search API — neural and keyword web search, page content retrieval, similarity search, and LLM-grounded answers. Endpoints include /search (find pages by meaning or keyword), /contents (fetch cleaned page text, highlights, and summaries), /findSimilar (semantically similar pages), and /answer (a sourced answer to a question). All calls are POST with a JSON body. Auth is handled automatically via the EXA_API_KEY environment variable, injected as the x-api-key header.",
+  "docsUrl": "https://docs.exa.ai/reference/getting-started",
+  "headers": {
+    "x-api-key": "${EXA_API_KEY}",
+    "Content-Type": "application/json"
+  },
+  "secrets": {
+    "EXA_API_KEY": "${EXA_API_KEY}"
+  },
+  "allowedEndpoints": ["https://api.exa.ai/**"],
+  "testConnection": {
+    "method": "POST",
+    "url": "https://api.exa.ai/search",
+    "body": {
+      "query": "drawlatch connection test",
+      "numResults": 1
+    },
+    "description": "Runs a minimal search query to verify the Exa API key"
+  }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wolpertingerlabs/drawlatch",
-  "version": "1.0.0-alpha.35",
+  "version": "1.0.0-alpha.37",
   "description": "Encrypted MCP proxy with mutual authentication. Local MCP server forwards requests through an encrypted channel to a remote secrets-holding server.",
   "type": "module",
   "workspaces": [