Feature

core/target-selection

Declares which way an AI gateway chooses among several targets that can serve the same request. Its strategy is latency, which picks the target observed to answer quickest, or cost, which picks the target that is cheapest to call. It is the choice between targets rather than the routing itself: which targets are candidates comes from the gateway's own routing table, so a table that publishes each model alias once leaves nothing to choose between. The developer attaches it in the Aggregate, since the strategy is a value, and a Release binds its realization in the Manifest. On core/gateway/litellm, target-selection-litellm writes latency as the proxy's routing strategy and refuses cost by name: the proxy's price table does not name OpenAI's and Anthropic's models in the provider/model form the gateway's targets take, so it would choose by order. On core/gateway/kong-enterprise and core/gateway/traefik-hub, target-selection-kong-enterprise and target-selection-traefik-hub halt every attachment, since each of their model routes carries one target. On core/gateway/higress, target-selection-higress halts every attachment, since the gateway can measure a service's latency but cannot make its choice route the request, and chooses no target by cost. On core/gateway/agentgateway, target-selection-agentgateway halts every attachment, since the gateway takes the quickest target only when a random draw picks it, and chooses no target by cost. Each halts on any other gateway.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:c7a10d9f41d54c0ad064c453ef2cfd8bd4a3b5c73bcb8c6ac4ecf4ba92c969d8
Published
2026-11-10T10:17:33Z
Signing identity
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signature

  • Officialapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:3343d53b93ceabea6203effc1027a397ff31888cfefe88cddc5515dcf0b057ba

Reference at this version

oci://hub.aggrega.ai/feature/core/target-selection:1.0.0
Applies to
gateway.aggrega.ai/intelligence=semantic
Conflicts with
—

Developer parameters

Values the developer sets when attaching this feature.

Extends BaseComponents#/schemas/BaseFeatureParameter

NameTypeDefaultRequiredDescription
strategystring (latency | cost)latencyyesHow the gateway chooses among the targets that can serve a request: latency, the target observed to answer quickest; or cost, the target cheapest to call.

Output contract

Values this feature publishes to consumers.

No output values declared.

Annotations

No annotations declared.

Relationships

Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.

Feature concept reference →

The Aggrega catalog — an open index of components, features, recipes, and the plugins that render them.

Built with the shared Aggrega design system.

Privacy