@hiper2d/ai-agents 0.36.0 → 0.36.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/index.d.mts +3 -2
- package/dist/index.d.ts +3 -2
- package/dist/index.js +1 -2
- package/dist/index.js.map +1 -1
- package/dist/index.mjs +1 -2
- package/dist/index.mjs.map +1 -1
- package/package.json +1 -1
package/dist/index.d.mts
CHANGED
|
@@ -382,8 +382,9 @@ declare const API_KEY_CONSTANTS: {
|
|
|
382
382
|
* Providers whose API ENFORCES a JSON schema on the answer (askWithZodSchema sends the
|
|
383
383
|
* schema natively and the provider constrains the output to it). The rest only get the
|
|
384
384
|
* schema described in the prompt: Grok, GLM and Fugu run in "JSON object" mode (valid JSON,
|
|
385
|
-
* any shape), DeepSeek and MiniMax have no JSON mode on these calls at all
|
|
386
|
-
*
|
|
385
|
+
* any shape), DeepSeek and MiniMax have no JSON mode on these calls at all, and Meta's
|
|
386
|
+
* json_schema runs with strict: false (the shape is guided, not guaranteed; a 2026-11-12
|
|
387
|
+
* probe also read 0% of a repeated prompt from cache there, so there is nothing to gain).
|
|
387
388
|
* Hosts use this to decide where a schema can replace a plain-text ask: on most enforcing
|
|
388
389
|
* providers the prompt cache is keyed on the output format, so a host that mixes text and
|
|
389
390
|
* schema calls loses the cache between them (measured 2026-11-12 on OpenAI, Mistral and
|
package/dist/index.d.ts
CHANGED
|
@@ -382,8 +382,9 @@ declare const API_KEY_CONSTANTS: {
|
|
|
382
382
|
* Providers whose API ENFORCES a JSON schema on the answer (askWithZodSchema sends the
|
|
383
383
|
* schema natively and the provider constrains the output to it). The rest only get the
|
|
384
384
|
* schema described in the prompt: Grok, GLM and Fugu run in "JSON object" mode (valid JSON,
|
|
385
|
-
* any shape), DeepSeek and MiniMax have no JSON mode on these calls at all
|
|
386
|
-
*
|
|
385
|
+
* any shape), DeepSeek and MiniMax have no JSON mode on these calls at all, and Meta's
|
|
386
|
+
* json_schema runs with strict: false (the shape is guided, not guaranteed; a 2026-11-12
|
|
387
|
+
* probe also read 0% of a repeated prompt from cache there, so there is nothing to gain).
|
|
387
388
|
* Hosts use this to decide where a schema can replace a plain-text ask: on most enforcing
|
|
388
389
|
* providers the prompt cache is keyed on the output format, so a host that mixes text and
|
|
389
390
|
* schema calls loses the cache between them (measured 2026-11-12 on OpenAI, Mistral and
|
package/dist/index.js
CHANGED
|
@@ -996,8 +996,7 @@ var SCHEMA_ENFORCING_API_KEYS = /* @__PURE__ */ new Set([
|
|
|
996
996
|
API_KEY_CONSTANTS.GOOGLE,
|
|
997
997
|
API_KEY_CONSTANTS.MISTRAL,
|
|
998
998
|
API_KEY_CONSTANTS.QWEN,
|
|
999
|
-
API_KEY_CONSTANTS.MOONSHOT
|
|
1000
|
-
API_KEY_CONSTANTS.META
|
|
999
|
+
API_KEY_CONSTANTS.MOONSHOT
|
|
1001
1000
|
]);
|
|
1002
1001
|
var SupportedAiKeyNames = {
|
|
1003
1002
|
[API_KEY_CONSTANTS.OPENAI]: "OpenAI",
|