@netlify/agent-runner-cli 1.135.0 → 1.135.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/bin-local.js +62 -62
- package/dist/bin.js +61 -61
- package/dist/index.js +60 -60
- package/dist/skills/netlify-ai-gateway/SKILL.md +8 -3
- package/package.json +1 -1
|
@@ -12,9 +12,14 @@ provider SDKs work without API keys or configuration.
|
|
|
12
12
|
|
|
13
13
|
## How It Works
|
|
14
14
|
|
|
15
|
-
Netlify
|
|
16
|
-
|
|
17
|
-
|
|
15
|
+
Netlify injects provider-specific environment variables at runtime, and official SDKs auto-detect them — a default
|
|
16
|
+
constructor like `new OpenAI()` works out of the box. Requests are proxied through AI Gateway and billed to your
|
|
17
|
+
Netlify account credits.
|
|
18
|
+
|
|
19
|
+
> [!IMPORTANT]
|
|
20
|
+
> Write AI functions with modern syntax — **v2** (`export default async (req: Request) => Response`) or **v3** (object
|
|
21
|
+
> export `satisfies NetlifyFunction`). Credentials are injected by the modern function runtime only: a legacy **v1**
|
|
22
|
+
> function (`exports.handler`) gets no key at runtime and 500s with "missing API key" even though the build passes.
|
|
18
23
|
|
|
19
24
|
Netlify **never overrides** environment variables you have already set. The check is per-provider: if you set your own
|
|
20
25
|
`OPENAI_API_KEY`, Netlify will not set `OPENAI_API_KEY` or `OPENAI_BASE_URL`, but will still inject Anthropic and
|