@duetso/agent 0.3.12 → 0.3.13

package/dist/src/model-resolution/duet-gateway.d.ts

@@ -1,4 +1,4 @@
-import { type Model } from "@earendil-works/pi-ai";
+import { type Api, type Model, type Provider, type ProviderAuth } from "@earendil-works/pi-ai";
 /** Request header the product reads to attribute a gateway call to a tier. */
 export declare const DUET_TIER_HEADER = "x-duet-tier";
 /**
@@ -13,64 +13,71 @@ export declare const DUET_TIER_HEADER = "x-duet-tier";
 export declare function duetTierHeaders(): Record<string, string> | undefined;
 /**
  * The Duet gateway proxies Vercel's AI Gateway path layout and authenticates
- * with a `DUET_API_KEY` token scoped to a single org. Rather than ship a
- * parallel model registry, the `duet-gateway` provider piggybacks on upstream
- * model definitions and only swaps `baseUrl` to point at Duet.
- *
- * `DUET_GATEWAY_BASE_URL` can point model traffic at a dedicated gateway
- * origin. When it is unset, model traffic goes directly to
+ * with a `DUET_API_KEY` token scoped to a single org. `DUET_GATEWAY_BASE_URL`
+ * points model traffic at a different origin; unset, it goes to
  * `https://gateway.duet.so`.
- *
- * Auth flows through pi-ai's existing vercel-ai-gateway path, which reads
- * `AI_GATEWAY_API_KEY` — the CLI shims that env var from `DUET_API_KEY` at
- * startup so users only need to set the duet token.
  */
 export declare const DUET_GATEWAY_API_KEY_ENV = "DUET_API_KEY";
 export declare const DUET_GATEWAY_BASE_URL_ENV = "DUET_GATEWAY_BASE_URL";
 export declare function getDuetGatewayBaseUrl(): string;
 /**
- * Resolve a `duet-gateway:<modelId>` string to a Model.
+ * A gateway route: where a request goes, and which credential it carries.
+ *
+ * The Duet gateway is a proxy in front of Vercel's — same catalog, same model
+ * ids, same protocols — so the origin and the credential are the entire
+ * difference between them. Every rule below is therefore written once against
+ * a route rather than twice per gateway, and a third gateway of this shape
+ * costs one entry rather than another parallel set of functions.
+ */
+export interface GatewayRoute {
+    id: string;
+    name: string;
+    /** Read per call: the Duet origin is configurable, Vercel's is fixed. */
+    origin(): string;
+    auth(): ProviderAuth;
+    /** Request headers the route needs on every model it serves. */
+    headers(): Record<string, string> | undefined;
+}
+export declare const GATEWAY_ROUTES: readonly GatewayRoute[];
+/** The route serving `providerId`, or undefined when it is not a gateway. */
+export declare function gatewayRoute(providerId: string): GatewayRoute | undefined;
+/**
+ * A gateway as a first-class pi-ai provider.
  *
- * Anthropic models use pi-ai's Vercel AI Gateway catalog because that path is
- * already Anthropic-native. OpenAI models intentionally use pi-ai's OpenAI
- * catalog and the Duet gateway's OpenAI-compatible route instead; routing them
- * through the Anthropic-compatible gateway path drops OpenAI reasoning stream
- * semantics, so the TUI never sees reasoning/thinking events.
+ * `auth` is why this is a provider rather than a bag of rewritten models: a
+ * credential is resolved per provider, and `duet-gateway` is not an id pi-ai's
+ * env-key map knows. Declaring it on the provider is what lets any call
+ * resolve the token without being handed one.
  *
- * Auth: the duet.so proxy only accepts `DUET_API_KEY`-style tokens and 500s on
- * a Vercel `vck_...` key. `resolveProviderApiKey("duet-gateway")` returns the
- * Duet token directly so the underlying transport always sends the right
- * credential, even when the user also has a real `AI_GATEWAY_API_KEY=vck_...`
- * set for explicit `vercel-ai-gateway:*` pins.
+ * All three transports are declared because serialization belongs to the
+ * provider: rewriting a model's `api` to one the provider does not implement
+ * yields a model that claims Responses and is sent as Anthropic, silently
+ * dropping reasoning effort and mangling tool-result images.
  */
-export declare function resolveDuetGatewayModel(modelId: string): Model<any>;
-/** Apply gateway capabilities that are newer than the pinned model catalog. */
-export declare function applyVercelGatewayModelOverrides(modelId: string, model: Model<any>): Model<any>;
+export declare function gatewayProvider(route: GatewayRoute): Provider;
 /**
- * Clone a known sibling on the same provider to build a Model pi-ai has not
- * shipped yet; returns undefined when the provider/modelId pair is not a
- * pending clone. Shared by the `duet-gateway` path (above) and direct
- * `vercel-ai-gateway`/`openrouter` resolution in resolver.ts. Delete a clone
- * entry once pi-ai ships that provider/model pair and it resolves directly.
+ * Resolve a `<gateway>:<modelId>` string to a Model.
+ *
+ * An id the catalog has not shipped still resolves: a gateway serves a model
+ * the moment its vendor lists it, and waiting for a catalog release to use it
+ * is the coupling this module exists to avoid. The synthesized entry is
+ * deliberately conservative so an unknown model never 400s on an
+ * over-advertised window.
  */
-export declare function resolveMissingModel(provider: string, modelId: string): Model<any> | undefined;
+export declare function resolveGatewayModel(route: GatewayRoute, modelId: string): Model<Api>;
 /**
- * Resolve the API key for a provider, including the project-local
- * `duet-gateway` provider that pi-ai's built-in env-key map does not
- * know about.
+ * The API key to send for a provider, resolved the way Duet stores keys.
  *
- * `resolveDuetGatewayModel` deliberately overrides `model.provider` to
- * `"duet-gateway"` so cost and usage telemetry attribute the call to
- * the Duet proxy rather than the upstream vercel-ai-gateway. The
- * tradeoff is that pi-ai's `getEnvApiKey(provider)` returns `undefined`
- * for `"duet-gateway"`, so the agent-loop's `getApiKey` callback and
- * any direct `complete()` call would silently send an empty API key
- * and fail with `Could not resolve authentication method` even when
- * `DUET_API_KEY` is set.
+ * Two kinds of caller need this. Connected providers (ChatGPT, Copilot) keep
+ * their token in Duet's own store, which pi-ai cannot see at all. And the
+ * api-dispatch `complete()` used for structured output does no provider auth
+ * resolution whatsoever, so it needs the key handed to it — including for
+ * `duet-gateway`, an id pi-ai's env-key map does not know.
  *
- * This wrapper closes the gap: `"duet-gateway"` returns the Duet token
- * directly, every other provider falls through to pi-ai's normal
- * env-key resolution unchanged.
+ * A gateway rebase deliberately rewrites `model.provider` to
+ * `"duet-gateway"` so cost and usage telemetry attribute the call to the Duet
+ * proxy rather than to Vercel; that rename is what puts the id outside pi-ai's
+ * map in the first place.
  */
 export declare function resolveProviderApiKey(provider: string): string | undefined;
 //# sourceMappingURL=duet-gateway.d.ts.map

package/dist/src/model-resolution/duet-gateway.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"duet-gateway.d.ts","sourceRoot":"","sources":["../../../src/model-resolution/duet-gateway.ts"],"names":[],"mappings":"AAAA,OAAO,EAA0B,KAAK,KAAK,EAAE,MAAM,uBAAuB,CAAC;AAQ3E,8EAA8E;AAC9E,eAAO,MAAM,gBAAgB,gBAAgB,CAAC;AAE9C;;;;;;;;GAQG;AACH,wBAAgB,eAAe,IAAI,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,GAAG,SAAS,CAGpE;AAkED;;;;;;;;;;;;;GAaG;AAEH,eAAO,MAAM,wBAAwB,iBAAiB,CAAC;AACvD,eAAO,MAAM,yBAAyB,0BAA0B,CAAC;AAEjE,wBAAgB,qBAAqB,IAAI,MAAM,CAI9C;AAED;;;;;;;;;;;;;;GAcG;AACH,wBAAgB,uBAAuB,CAAC,OAAO,EAAE,MAAM,GAAG,KAAK,CAAC,GAAG,CAAC,CAenE;AAuBD,+EAA+E;AAC/E,wBAAgB,gCAAgC,CAAC,OAAO,EAAE,MAAM,EAAE,KAAK,EAAE,KAAK,CAAC,GAAG,CAAC,GAAG,KAAK,CAAC,GAAG,CAAC,CAY/F;AA+GD;;;;;;GAMG;AACH,wBAAgB,mBAAmB,CAAC,QAAQ,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,GAAG,KAAK,CAAC,GAAG,CAAC,GAAG,SAAS,CAY7F;AA4CD;;;;;;;;;;;;;;;;;GAiBG;AACH,wBAAgB,qBAAqB,CAAC,QAAQ,EAAE,MAAM,GAAG,MAAM,GAAG,SAAS,CAU1E"}
+{"version":3,"file":"duet-gateway.d.ts","sourceRoot":"","sources":["../../../src/model-resolution/duet-gateway.ts"],"names":[],"mappings":"AAAA,OAAO,EAGL,KAAK,GAAG,EACR,KAAK,KAAK,EACV,KAAK,QAAQ,EACb,KAAK,YAAY,EAClB,MAAM,uBAAuB,CAAC;AAa/B,8EAA8E;AAC9E,eAAO,MAAM,gBAAgB,gBAAgB,CAAC;AAE9C;;;;;;;;GAQG;AACH,wBAAgB,eAAe,IAAI,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,GAAG,SAAS,CAGpE;AAQD;;;;;GAKG;AACH,eAAO,MAAM,wBAAwB,iBAAiB,CAAC;AACvD,eAAO,MAAM,yBAAyB,0BAA0B,CAAC;AAEjE,wBAAgB,qBAAqB,IAAI,MAAM,CAI9C;AAED;;;;;;;;GAQG;AACH,MAAM,WAAW,YAAY;IAC3B,EAAE,EAAE,MAAM,CAAC;IACX,IAAI,EAAE,MAAM,CAAC;IACb,yEAAyE;IACzE,MAAM,IAAI,MAAM,CAAC;IACjB,IAAI,IAAI,YAAY,CAAC;IACrB,gEAAgE;IAChE,OAAO,IAAI,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,GAAG,SAAS,CAAC;CAC/C;AAyBD,eAAO,MAAM,cAAc,EAAE,SAAS,YAAY,EAAmC,CAAC;AAEtF,6EAA6E;AAC7E,wBAAgB,YAAY,CAAC,UAAU,EAAE,MAAM,GAAG,YAAY,GAAG,SAAS,CAEzE;AA0GD;;;;;;;;;;;;GAYG;AACH,wBAAgB,eAAe,CAAC,KAAK,EAAE,YAAY,GAAG,QAAQ,CAa7D;AAED;;;;;;;;GAQG;AACH,wBAAgB,mBAAmB,CAAC,KAAK,EAAE,YAAY,EAAE,OAAO,EAAE,MAAM,GAAG,KAAK,CAAC,GAAG,CAAC,CAUpF;AAmCD;;;;;;;;;;;;;GAaG;AACH,wBAAgB,qBAAqB,CAAC,QAAQ,EAAE,MAAM,GAAG,MAAM,GAAG,SAAS,CAU1E"}