@axiom-lattice/protocols 4.5.0 → 4.6.0
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/.turbo/turbo-build.log +10 -10
- package/CHANGELOG.md +53 -0
- package/dist/index.d.mts +662 -1
- package/dist/index.d.ts +662 -1
- package/dist/index.js +19 -0
- package/dist/index.js.map +1 -1
- package/dist/index.mjs +17 -0
- package/dist/index.mjs.map +1 -1
- package/package.json +1 -1
- package/src/ModelLatticeProtocol.ts +10 -0
- package/src/ModelProviderProtocol.ts +821 -0
- package/src/index.ts +1 -0
package/package.json
CHANGED
|
@@ -29,6 +29,16 @@ export interface LLMConfig {
|
|
|
29
29
|
extra?: Record<string, any>;
|
|
30
30
|
/** Whether the model supports vision/image inputs for multimodal processing */
|
|
31
31
|
supportsVision?: boolean;
|
|
32
|
+
/**
|
|
33
|
+
* Send requests through OpenAI's Responses API (`/v1/responses`) instead of
|
|
34
|
+
* Chat Completions (`/v1/chat/completions`).
|
|
35
|
+
*
|
|
36
|
+
* These are different paths with different request fields (`input` vs
|
|
37
|
+
* `messages`), so an endpoint that speaks only one of them fails with
|
|
38
|
+
* unrecognised parameters or a missing route when sent the other. Defaults to
|
|
39
|
+
* Chat Completions, which is what every OpenAI-compatible upstream supports.
|
|
40
|
+
*/
|
|
41
|
+
useResponsesApi?: boolean;
|
|
32
42
|
}
|
|
33
43
|
|
|
34
44
|
/**
|