> ## Documentation Index
> Fetch the complete documentation index at: https://docs.streamkap.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Agent Connections

> Get the tenant's saved agent connections.

Returns the bulk shape (LLM / MCP / HTTP connection arrays). Secrets
are masked (``sk-a****xyzw`` partial mask for apiKey/clientSecret;
``********`` for bearerToken/headerValue and every value inside a
``headers`` dict), so ``read:agents`` is the correct gate - a team
member with read-only access can see which connections exist to
reason about agent configuration without being able to mutate them.
The unmasked plaintext is only reachable via the internal
``_load_agent_connections_decrypted`` helper used at deploy time -
never via an HTTP endpoint.



## OpenAPI

````yaml /openapi/openapi.json get /agents/connections
openapi: 3.1.0
info:
  title: Streamkap REST API
  description: >-
    The Streamkap REST API allows you to programmatically manage your CDC
    pipelines, sources, destinations, transforms, and more.


    Authenticate using a bearer token obtained from the [Access
    Token](/api-reference/auth/access-token) endpoint with your API client
    credentials.
  contact:
    name: Streamkap Support
    url: https://streamkap.com/
    email: support@streamkap.com
  license:
    name: Proprietary
  version: 2.0.0
servers:
  - url: https://api.streamkap.com
    description: Production
security: []
tags:
  - name: Agents
    description: Create, deploy, and manage Flink-based AI agents.
  - name: Agents Observability
    description: >-
      Read-only views over the MCP audit log: agent rollup, sessions, spans,
      histograms, external-agent verify.
  - name: Alerts
    description: Manage alert subscribers, preferences, and notification credentials.
  - name: Authentication
    description: Obtain and refresh access tokens, manage client credentials and roles.
  - name: Billing
    description: Retrieve usage metrics, summaries, and export billing data.
  - name: Consumer Groups
    description: List, inspect, and reset Kafka consumer group offsets.
  - name: Dashboard
    description: Retrieve organisation-level statistics and overview data.
  - name: Destinations
    description: Create, configure, and manage data destinations and their lifecycle.
  - name: Kafka Access
    description: Manage Kafka users and their access permissions.
  - name: Logs
    description: Query and summarise system logs.
  - name: Pipelines
    description: Create, configure, and manage CDC pipelines and their lifecycle.
  - name: Project Keys
    description: Manage project keys that bundle API credentials and optional Kafka access.
  - name: Schema Registry
    description: Browse schema subjects, versions, and retrieve schema definitions.
  - name: Services
    description: View and switch service metadata.
  - name: Sources
    description: >-
      Create, configure, and manage data sources, snapshots, and their
      lifecycle.
  - name: Tags
    description: Create, update, and manage resource tags for organisation.
  - name: Topics
    description: Browse topic details, statistics, configurations, metrics, and messages.
  - name: Transforms
    description: >-
      Create, deploy, and manage data transforms, unit tests, and implementation
      details.
paths:
  /agents/connections:
    get:
      tags:
        - Agents
      summary: Get Agent Connections
      description: |-
        Get the tenant's saved agent connections.

        Returns the bulk shape (LLM / MCP / HTTP connection arrays). Secrets
        are masked (``sk-a****xyzw`` partial mask for apiKey/clientSecret;
        ``********`` for bearerToken/headerValue and every value inside a
        ``headers`` dict), so ``read:agents`` is the correct gate - a team
        member with read-only access can see which connections exist to
        reason about agent configuration without being able to mutate them.
        The unmasked plaintext is only reachable via the internal
        ``_load_agent_connections_decrypted`` helper used at deploy time -
        never via an HTTP endpoint.
      operationId: getAgentConnections
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties: true
                type: object
                title: Response Getagentconnections
      security:
        - FronteggHTTPAuthentication: []
components:
  securitySchemes:
    FronteggHTTPAuthentication:
      type: http
      scheme: bearer

````