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

Component

core/ai-agent/a2a-remote

An agent another party runs and publishes over the Agent2Agent (A2A) protocol, reached at the address its Agent Card lists. Nothing is provisioned or run. Both realizations are references publishing what a consumer needs: the agent's address, where its card is read, the URL scheme, the header a caller's credential goes under, and where a caller obtains a token. The Release names the address in infra.endpoint, which carries no default: the URL of an interface the card lists for a binding served over HTTP, without any part carrying a key. The card is read at the well-known location on that address's scheme and host, and the header is Authorization, unless infra.agent_card_url and infra.credential_header name others; infra.token_url, infra.oidc_discovery_url and infra.scopes, each optional, copy what the card declares for OAuth 2.0 client credentials or OpenID Connect. No credential is held here: each consumer holds its own on its connection, as it belongs to the consumer, not the address. core/ai-tool/agent-invocation's container presents under that header the whole value a Secret holds, for an API key in a header or cookie or an HTTP scheme such as Bearer or Basic; a token it obtains with a client secret by the OAuth 2.0 client-credentials grant, directly or through OpenID Connect; and, for mutual TLS, a client certificate mounted from a Secret its connection names, the card naming none to publish here. That tool halts the build on a credential or client secret for an http endpoint. Not covered: a key in the query string, an HTTP scheme answering a challenge, such as Digest, and other OAuth 2.0 grants. Reach for helm/a2a-remote on Kubernetes, compose/a2a-remote under Docker Compose.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:28f2fb63e865f53ee13e71986a82a749332312ef4eadb33fe34dd176ed86e6c6
Publicado
2026-11-10T10:07:08Z
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:529bb70c4be62b4b76ae3e3b2a203b5c664fe44509a420c4397dc9ec76d57901

Referencia en esta versión

oci://hub.aggrega.ai/component/core/ai-agent/a2a-remote:1.0.0

Parámetros del desarrollador

Valores que el desarrollador establece en el Aggregate.

Extiende BaseComponents#/schemas/BaseAgentParameter

Dimensionamiento del operador

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

NombreTipoPredeterminadoObligatorioDescripción
endpointstring—noThe http or https URL of an interface the agent's card lists in supportedInterfaces for a binding served over HTTP (protocolBinding JSONRPC or HTTP+JSON), for example https://agent.example.com/a2a/v1, without any part that carries a key: at least its scheme and host. The realizations publish it as written. An http address is published too, but core/ai-tool/agent-invocation halts the build on a credential or client_secret held on its connection to an agent published at one, since the credential, or the token obtained with the secret, would reach the agent unencrypted.
agent_card_urlstring—noThe URL the agent's card is read at, where it is not the well-known location /.well-known/agent-card.json on infra.endpoint's scheme and host, which the realizations publish when this is unset.
credential_headerstringAuthorizationnoThe request header the agent reads a caller's credential from, which the realizations publish for a consumer to present its credential under: the header an API-key security scheme in the agent's card names, Cookie where that scheme places its key in a cookie, or Authorization for an HTTP authentication scheme. core/ai-tool/agent-invocation presents under it the whole value the Secret on its connection holds, so it reaches an API key in a header; one in a cookie, the Secret holding the cookie's name, "=" and the key; and an HTTP scheme whose value is fixed, the Secret holding the scheme's name, a space and the credential, as "Bearer " and a token, or "Basic " and the Base64 encoding of the user name and password joined by a colon. It does not reach an API key the card places in the query string, nor an HTTP scheme whose value answers a challenge from the agent, such as Digest.
token_urlstring—noThe https URL a caller obtains an access token from with the OAuth 2.0 client-credentials grant: the tokenUrl of the clientCredentials flow in an oauth2 security scheme the agent's card declares.
oidc_discovery_urlstring—noThe https OpenID Connect discovery URL an openIdConnect security scheme in the agent's card names as its openIdConnectUrl, from which a caller reads the provider's token endpoint.
scopesstring—noThe scopes a caller requests its token for, separated by spaces as in OAuth 2.0's scope parameter, for example "agent.read agent.invoke": those the card's security requirements list for its OAuth 2.0 or OpenID Connect scheme.

Contrato de salida

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

NombreTipoPredeterminadoObligatorioDescripción
endpointstring—síThe URL a caller sends A2A requests to: infra.endpoint as the Release wrote it, the address without any part that carries a key.
agent_card_urlstring—síThe URL the agent's card is read at, which describes the agent's skills, interfaces and security schemes: infra.agent_card_url where the Release sets it, otherwise /.well-known/agent-card.json on the endpoint's scheme and host.
protocolstring—noURL scheme of `endpoint`, http or https.
credential_headerstring—noThe request header a consumer presents its credential under, where the agent checks one: Authorization unless the Release names another in infra.credential_header. The credential itself is the consumer's, held on its own connection to the agent.
token_urlstring—noThe URL a caller obtains an access token from with the OAuth 2.0 client-credentials grant: infra.token_url as the Release wrote it, or empty where the agent's card declares no such scheme.
oidc_discovery_urlstring—noThe OpenID Connect discovery URL a caller reads the provider's token endpoint from: infra.oidc_discovery_url as the Release wrote it, or empty where the agent's card declares no such scheme.
scopesstring—noThe scopes a caller requests its token for, separated by spaces: infra.scopes as the Release wrote it, or empty.

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.

No se declararon sockets uses.

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

No se declararon canales de autoinyección.

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