| name | appnz-provider-exa |
| description | Use this skill when the user asks to use Exa or provider exa integration through app.nz; covers model selection when present, BYOK setup, OpenAI-compatible routing, provider-specific endpoints, aliases, and debugging gateway headers. |
Exa on app.nz
Route Exa through app.nz with one app.nz key. Use this skill when a user asks for Exa, exa, one of its model ids, aliases, product integrations, or BYOK setup for this provider.
Workflow
- Use
/api/gateway/models?provider=exa to confirm the current public model list if exact availability matters.
- Call app.nz at
https://app.nz/v1 with Authorization: Bearer pk_live_...; do not call https://api.exa.ai directly unless the user explicitly asks to bypass app.nz.
- Store a user-owned upstream key with
POST /api/gateway/provider-keys using provider exa when BYOK is required. The upstream secret is never returned by app.nz.
- This provider is declared for product or backend integration rather than direct model-catalogue routing; use the related app.nz API skill for the public endpoint.
- Read
X-Gateway-Provider and X-Gateway-Model response headers when debugging routing.
BYOK
curl -sX POST https://app.nz/api/gateway/provider-keys \
-H "Authorization: Bearer pk_live_..." \
-H "Content-Type: application/json" \
-d '{"provider":"exa","api_key":"REDACTED_UPSTREAM_KEY"}'
Models
No direct model catalogue entries are currently routed for this provider. Check the product API surface that uses it, such as search, papers, or app.nz control-plane endpoints.
