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

# Check if account is registered

> Check if an account is registered and return its target chain and token if registered



## OpenAPI

````yaml https://raw.githubusercontent.com/rhinestonewtf/openapi/refs/heads/main/deposit-service.json get /check/{address}
openapi: 3.1.0
info:
  title: Deposit Service API
  version: 1.0.0
  description: >-
    Cross-chain deposit processing service with automatic token bridging and gas
    sponsorship
servers:
  - url: https://v1.orchestrator.rhinestone.dev/deposit-processor
security: []
paths:
  /check/{address}:
    get:
      tags:
        - Accounts
      summary: Check if account is registered
      description: >-
        Check if an account is registered and return its target chain and token
        if registered
      parameters:
        - schema:
            type: string
            pattern: ^0x[a-fA-F0-9]{40}$
            description: Ethereum address (0x followed by 40 hex characters)
            example: '0x742d35Cc6634C0532925a3b844Bc9e7595f5bE91'
          required: true
          description: Ethereum address (0x followed by 40 hex characters)
          name: address
          in: path
      responses:
        '200':
          description: Account registration status
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CheckResponse'
        '400':
          description: Invalid address format
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    CheckResponse:
      type: object
      properties:
        isRegistered:
          type: boolean
          description: >-
            Whether the EVM account is registered. EVM-scoped (legacy): a
            Solana/Tron-only account reads `false` here. Use `sources` for
            per-chain registration across all namespaces.
        targetChain:
          type: string
        targetToken:
          type: string
        recipient:
          type: string
        sourceChains:
          type: array
          items:
            type: string
        outputTokenRules:
          type: array
          items:
            $ref: '#/components/schemas/OutputTokenRule'
        rejectUnmapped:
          type: boolean
        sources:
          type: array
          items:
            type: object
            properties:
              chain:
                type: string
              depositAddress:
                type: string
            required:
              - chain
              - depositAddress
          description: >-
            Every chain this account can receive deposits from — CAIP-2 id +
            deposit address — uniform across EVM, Solana, and Tron. A chain is
            present iff the account is registered for it (the canonical
            per-source registration signal); absence means not registered. EVM
            chains share the account address; Solana/Tron carry their own.
            Always present (may be empty).
      required:
        - isRegistered
        - sources
    ErrorResponse:
      type: object
      properties:
        error:
          type: string
        details:
          type: array
          items:
            type: object
            properties:
              message:
                type: string
              path:
                type: array
                items:
                  anyOf:
                    - type: string
                    - type: number
              code:
                type: string
            required:
              - message
      required:
        - error
    OutputTokenRule:
      type: object
      properties:
        match:
          $ref: '#/components/schemas/OutputTokenRuleMatch'
        outputToken:
          type: string
          minLength: 1
      required:
        - match
        - outputToken
      description: >-
        Destination token routing rule. Matches deposits by source token
        attributes and selects the target-chain output token.
      example:
        match:
          symbol: USDC
        outputToken: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913'
    OutputTokenRuleMatch:
      type: object
      properties:
        chain:
          type: string
          pattern: ^[a-z0-9]+:[a-zA-Z0-9]+$
          description: CAIP-2 chain identifier (e.g. "eip155:8453")
          example: eip155:8453
        token:
          type: string
          minLength: 1
        symbol:
          type: string
      description: >-
        Source-token match criteria. Rules may match by source chain, source
        token address, source symbol, or a combination.
      example:
        chain: eip155:10
        symbol: USDC

````