Esta página se tradujo automáticamente. Leer el original en inglés.

Component

core/ai-tool/agent-invocation

A tool letting one agent delegate a step to another over an agent-to-agent protocol, A2A by default: the caller waits synchronously for a result, asynchronously for a handle it polls, or not at all, fire-and-forget. Its required agent socket resolves the target by topology, not prompt. Marked mutating: a delegated agent may act in the world. Realized on Kubernetes as a Knative Service scaled to zero between calls yet admitting each, it publishes a host, port, endpoint and protocol for a consumer to wire to. The catalog pins no image, so nothing renders until the Release sets `infra.image`. The agent's address reaches the tool's code under default variable names; an `inject:` block on the connection delivers instead, as variables or files, the names that code reads. The component's own `inject:` block adds `env` and `file` entries beside them, and one reading a tool value alone replaces that value's default name. The connection may hold a credential, presented under the agent's published credential_header, its Secret holding the whole value: an API key in a header or cookie, or an HTTP scheme such as Bearer or Basic; a client_secret, for the OAuth 2.0 client-credentials grant, directly or through OpenID Connect; and, for mutual TLS, a client_certificate, mounted as files. A server_ca, also mounted, names the agent's server certificate authority. The build halts on a connection to an agent labelled managed with none of credential, client_secret, client_certificate or unauthenticated: true, and on a credential or client_secret to one labelled external publishing protocol http; to an agent inside the Release, http carries the credential or token unencrypted on the cluster network.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:71f2e29f01cce29f360bc23b17e3d1e64bab3af72bdcb266a219be8e42b538d0
Publicado
2026-11-10T10:09:46Z
Identidad de firma
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Firma

  • Oficialapplication/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:26a851d77c1bcfa5b0a18dea6d5db46a1bc633c586bf5d0857a121f462c92071

Referencia en esta versión

oci://hub.aggrega.ai/component/core/ai-tool/agent-invocation:1.0.0

Parámetros del desarrollador

Valores que el desarrollador establece en el Aggregate.

Extiende BaseComponents#/schemas/BaseToolParameter

NombreTipoPredeterminadoObligatorioDescripción
protocolstringa2así—
execution_modestring (synchronous | asynchronous | fire_and_forget)synchronoussí—

Dimensionamiento del operador

Dimensionamiento de la infraestructura que el operador ajusta para cada entorno.

NombreTipoPredeterminadoObligatorioDescripción
imagestring—noContainer image serving the delegation over HTTP.
portinteger (min 1024, max 65535)8080noPort the tool's own container listens on. A consumer does not necessarily connect here: the realization publishes the address callers use, and a control plane that fronts the tool routes from its own port to this one.
computeobject—no—
min_replicasinteger (min 0)0noReplica floor. Zero is what lets the tool run no replicas between calls, which the realization reaches through its control plane.
max_replicasinteger (min 1)5noReplica ceiling the realization's autoscaler may reach.
control_plane_presentbooleanfalsenoOperator affirmation that Knative Serving, the control plane the realization needs, is installed in the target cluster. The build halts unless this is set true, so a custom resource is never emitted as an orphan into a cluster that cannot reconcile it.
overridesobject (open)—noRealization-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Contrato de salida

Valores que este componente publica para los consumidores a través de la topología uses.

NombreTipoPredeterminadoObligatorioDescripción
hoststring—síIn-cluster DNS name an agent calls to delegate a step to the wired agent. A consumer that composes its own address dials this name; one that does not reads `endpoint` instead.
portinteger—síTCP port the delegation is accepted on. The realization fronts the tool on the control plane's own port rather than the tool container's, so a consumer reads this rather than the port an operator set.
endpointstring—síFull base URL an agent posts a delegation to, with the host and the port already composed. A consumer hands it to its tool client as the address it calls.
protocolstring—noURL scheme to reach `host` and `port` over, for a consumer composing its own address rather than reading `endpoint`.

Sockets uses

Los sockets de dependencia a través de los cuales se conecta este componente. El destino de cada conexión cableada a través de un socket debe satisfacer su selector de etiquetas, y cada conexión puede llevar un acoplamiento en los slots que declara el socket. Cada conexión que el Aggregate o la Release cablea a través del socket debe llenar los slots obligatorios.

target_agent

Selector
component.aggrega.ai/category=ai-agent
Inyección
env, file

Slots que cada conexión a través de este socket puede llenar

SlotSelectorObligatorioInyecciónSensibleDescripción
credentialfeature.aggrega.ai/kind=secretnoenvsíOptional credential the tool presents to the agent this connection reaches, under the request header that agent publishes as credential_header. When attached, the Recipe delivers it to the tool's container as AGENT_TOOL_TARGET_CREDENTIAL, a Kubernetes secretKeyRef to the Secret the credential publishes, and, on a connection writing no inject block, the header as AGENT_TOOL_TARGET_CREDENTIAL_HEADER where the agent publishes one; a credential publishing no Secret name and data key halts the build, and so does one on a connection to an agent labelled component.aggrega.ai/hosting external that publishes protocol http, to which it would travel unencrypted. An agent inside the Release that publishes protocol http receives it unencrypted on the cluster network. The Secret's value is the whole header value, delivered unchanged for the container to present as it is, with no prefix added: the key, for an API key the agent's card places in a header; the cookie's name, "=" and the key, under a credential_header of Cookie, for one it places in a cookie; and the scheme's name, a space and the credential, as "Bearer " and a token, for an HTTP scheme whose value is fixed, such as Bearer or Basic. An API key the card places in the query string, an HTTP scheme whose value answers a challenge from the agent, such as Digest, and two header credentials required together are not covered; OAuth 2.0 and OpenID Connect take client_secret, and mutual TLS client_certificate. Fill it with core/referenced-secret mapped to helm/k8s-existing-secret, naming a Secret the namespace already holds: a realization that names its Secret after the tool, such as k8s-external-secret or k8s-secret-from-parameter, halts the build here, because the Recipe renders its Service from an artifacts template and gives the tool no rendered name. Unattached, the tool runs without an injected credential.
client_secretfeature.aggrega.ai/kind=secretnoenvsíOptional client secret the tool's container sends, with client_id, to the agent's authorization server to obtain an access token by the OAuth 2.0 client-credentials grant, at the token_url the agent publishes or the token endpoint its oidc_discovery_url names. Delivered as AGENT_TOOL_TARGET_CLIENT_SECRET, a Kubernetes secretKeyRef to the Secret it publishes, beside AGENT_TOOL_TARGET_CLIENT_ID and AGENT_TOOL_TARGET_AUDIENCE and, on a connection writing no inject block, AGENT_TOOL_TARGET_TOKEN_URL, AGENT_TOOL_TARGET_OIDC_DISCOVERY_URL and AGENT_TOOL_TARGET_SCOPES, each where it has a value. Obtaining, caching and refreshing the token, and presenting it on each request, are the container's. The other OAuth 2.0 flows a card may declare, authorization code, device code, implicit and password, are not covered. The build halts on a client_secret with no client_id, on one wired to an agent publishing neither token_url nor oidc_discovery_url, on either address when it is not an https URL naming a host or carries a user name or password, and on one wired to an agent labelled component.aggrega.ai/hosting external that publishes protocol http, to which the token obtained with it would travel unencrypted. An agent inside the Release that publishes protocol http receives the token unencrypted on the cluster network. Fill it as credential is filled; it may sit beside credential on one connection.
client_certificatefeature.aggrega.ai/kind=secretnofilesíOptional client certificate the tool's container presents in the TLS handshake to an agent whose card requires mutual TLS. Its Secret holds tls.crt, the certificate, and tls.key, its private key, as a kubernetes.io/tls Secret does. The Recipe mounts the whole Secret read-only into the tool's container and delivers AGENT_TOOL_TARGET_CLIENT_CERT_FILE and AGENT_TOOL_TARGET_CLIENT_KEY_FILE naming the two files; presenting the certificate, and reading the files again when a renewal updates them, are the container's. The build halts on a client_certificate publishing no Secret name, on one wired to an agent publishing protocol http, and on one wired to an agent publishing no protocol and an endpoint that is not an https URL. Fill it with core/referenced-secret mapped to helm/k8s-existing-secret, naming a Secret the namespace already holds; the data key it publishes is not read, since the whole Secret is mounted. It may sit beside credential or client_secret on one connection.
server_cafeature.aggrega.ai/kind=secretnofilesíOptional authority the tool's container checks the agent's server certificate against, where the image does not already trust the authority that signs it. Its Secret holds ca.crt: the agent's server authority, not the issuer of a client certificate, so a ca.crt written beside a client certificate is not this one. The Recipe mounts the whole Secret read-only into the tool's container and delivers AGENT_TOOL_TARGET_SERVER_CA_FILE naming the file; checking the agent's certificate against it is the container's. It serves a connection holding any credential, or none. The build halts on a server_ca publishing no Secret name, on one wired to an agent publishing protocol http, and on one wired to an agent publishing no protocol and an endpoint that is not an https URL. Fill it as client_certificate is filled.

Slots de acoplamiento

Puntos de enlace con nombre en los que una Feature se acopla a este componente. El selector de un slot restringe qué Feature puede llenarlo y su lista inject indica cómo puede entregarse el material de la Feature. Un slot obligatorio debe estar enlazado en cada instancia, mediante un acoplamiento en la instancia o en un ámbito superior, y un slot sensible se declara para manejar material secreto. Una Feature también puede acoplarse con un nombre que ningún slot declara.

No se declararon slots de acoplamiento.

Lista de permitidos de autoinyección

env, file

Relaciones

Aristas tipadas hacia y desde otras entidades publicadas. Una referencia sin un destino publicado se muestra como una arista rota en lugar de como un enlace.

Usa

Usado por

Referencia del concepto Component →

El catálogo de Aggrega — un índice abierto de componentes, funcionalidades, recetas y los plugins que los renderizan.

Creado con el sistema de diseño compartido de Aggrega.

Privacidad