이 페이지는 기계 번역되었습니다. 영어 원문 읽기.

Feature

core/semantic-caching

Lets an AI gateway answer a prompt from the replies it stored earlier when the prompt is close enough in meaning to one it answered before, rather than calling the model again. The gateway turns each prompt into a vector with embedding_model, serves a stored reply whose prompt is at least similarity_threshold alike, and keeps a reply for ttl_seconds. scope decides who shares a cache. With key, every caller presenting the same key to the gateway is served from one cache, so an end user behind that key can be served a reply generated for another, tool calls included. The default, end_user, keeps each end user the gateway identifies apart. A match on meaning suits single prompts: on multi-turn or agentic traffic consecutive turns read alike, so a reply to an earlier turn can be served for a later one. It does not meet core/data-masking on one component. The developer attaches it in the Aggregate, with its inputs in values; it takes no infra. core/gateway/litellm, azure-api-management, apisix and traefik-hub realize it, the last three keeping scope key alone, apisix and traefik-hub for the callers each Release declares; litellm, apisix and traefik-hub keep the replies in a core/datastore/redis wired to the gateway, litellm requiring its administrative key. On core/gateway/kong-enterprise and higress every attachment halts, naming the caller separation each cache lacks, and on agentgateway, naming the reply cache it lacks; on any component but these seven an attachment halts naming the type, rendering nothing.

출처

공식이 카탈로그가 공식 게시자로 인정하는 서명 ID로 서명되었습니다.
콘텐츠 다이제스트
sha256:bac81b4175f269b56678e2188d363229d5d8028c18c7928702a321bc90c751c1
게시일
2026-11-10T10:17:27Z
서명 ID
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

서명

  • 공식application/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:f7c90cc58a5dd4682daeea38a0b260125ad4758a8f36a5b1811b67ff7cacdfb6

이 버전의 참조

oci://hub.aggrega.ai/feature/core/semantic-caching:1.0.0
적용 대상
gateway.aggrega.ai/intelligence=semantic
충돌 대상
—

개발자 매개변수

이 기능을 첨부할 때 개발자가 설정하는 값입니다.

BaseComponents#/schemas/BaseFeatureParameter 확장

이름타입기본값필수설명
similarity_thresholdnumber (min 0, max 1)—예How alike a prompt must be to one answered before for the stored reply to be served: the cosine similarity of their two vectors, from 0 to 1, where 1 is identical. A higher value serves fewer and closer matches; which value suits depends on embedding_model.
embedding_modelstring (min 1)—예The model that turns a prompt into the vector compared, named as the gateway knows it: an alias of the model map on an AI gateway, or on Azure API Management the id of a backend the instance holds for an embeddings model. Each realization refuses a name its gateway does not publish wherever the build can see what the gateway publishes; an instance's backends are not in the build, so the Azure API Management realization takes the id as written.
ttl_secondsinteger (min 1)—예How long a stored reply stays usable, in seconds.
scopestring (key | end_user)end_user아니요Who shares one cache. end_user, the default: each end user the gateway identifies has a cache of its own, so none is served a reply generated for another. key: every caller presenting the same key to the gateway shares one cache, so a reply generated for one end user behind that key can be served to another sending a similar prompt. Each realization says how its gateway identifies an end user and what it does with a request naming none, and refuses end_user where its gateway cannot keep end users apart.

출력 계약

이 기능이 소비자에게 게시하는 값입니다.

선언된 출력 값이 없습니다.

어노테이션

선언된 어노테이션이 없습니다.

관계

게시된 다른 엔터티와 주고받는 타입 지정 에지입니다. 게시된 대상이 없는 참조는 링크가 아닌 끊어진 에지로 표시됩니다.

Feature 개념 레퍼런스 →

Aggrega 카탈로그 — 컴포넌트, 기능, 레시피, 그리고 이를 렌더링하는 플러그인의 공개 인덱스입니다.

공유 Aggrega 디자인 시스템으로 구축되었습니다.

개인정보 보호