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

# Get bridge router and DEX provider metadata



## OpenAPI

````yaml /openapi.json get /v3/swap/providers
openapi: 3.0.0
info:
  title: Socket V3 Swap API Explorer
  description: V3 swap quote, status, and metadata endpoints
  version: '1.0'
  contact: {}
servers:
  - url: https://public-backend.socket.tech
    description: Production
security: []
tags: []
paths:
  /v3/swap/providers:
    get:
      tags:
        - Supported Chains & Token List
      summary: Get bridge router and DEX provider metadata
      operationId: V3SwapMetadataController_providers
      parameters:
        - name: includeDepositRoutes
          required: false
          in: query
          description: When true, include deposit route providers such as Bungee Auto.
          schema:
            example: 'true'
            type: string
            enum:
              - 'true'
              - 'false'
            default: 'true'
      responses:
        '200':
          description: Bridge router and DEX provider metadata for v3 swap.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V3SwapProvidersResponseDto'
components:
  schemas:
    V3SwapProvidersResponseDto:
      type: object
      properties:
        bridges:
          description: Bridge routers available through v3 swap.
          type: array
          items:
            $ref: '#/components/schemas/V3SwapProviderDto'
        dexes:
          description: DEX providers available through v3 swap.
          type: array
          items:
            $ref: '#/components/schemas/V3SwapProviderDto'
      required:
        - bridges
        - dexes
    V3SwapProviderDto:
      type: object
      properties:
        providerId:
          type: string
          description: Provider ID used by v3 swap APIs.
          example: rfq-vault-executor
        displayName:
          type: string
          description: Human-readable provider name.
          example: Socket Intents
        logoURI:
          type: string
          description: Provider logo URI.
          example: https://media.socket.tech/bridges/socket-icon.png
      required:
        - providerId
        - displayName
        - logoURI

````