create-zuplo-api 6.74.7 → 6.74.8
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.
|
@@ -2,13 +2,15 @@
|
|
|
2
2
|
|
|
3
3
|
This project is a Zuplo AI Gateway. It exposes the canonical AI Gateway
|
|
4
4
|
operations (`/v1/chat/completions`, `/v1/messages`, `/v1/responses`, and
|
|
5
|
-
`/v1/embeddings`) through `aiGatewayHandlerV2`
|
|
6
|
-
with an AI Gateway application API key (`ai-gateway-auth-v2-inbound`).
|
|
5
|
+
`/v1/embeddings`) through `aiGatewayHandlerV2` under `/{app_id}/v1/*`.
|
|
7
6
|
|
|
8
|
-
Each route
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
pre-declared in `config/policies.json`.
|
|
7
|
+
Each route invokes `ai-gateway-configuration-executor-v2-inbound`, which loads
|
|
8
|
+
the application's configuration from the `app_id` path segment and runs its
|
|
9
|
+
`inboundPolicyChain`. Applications may select only from the policies
|
|
10
|
+
pre-declared in `config/policies.json`. To require application API keys for a
|
|
11
|
+
specific app, add `ai-gateway-auth-v2-inbound` to that application's
|
|
12
|
+
`inboundPolicyChain`. Adding it on the route before the executor requires a
|
|
13
|
+
key for every application on the route.
|
|
12
14
|
|
|
13
15
|
## Customizing the gateway
|
|
14
16
|
|