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

# Transfer

> Allows the client to transfer an account created using the Agent API to another application,  such as Neuro-Access.

## Overview

Allows the client to transfer an account created using the Agent API to another application,  such as Neuro-Access. If the account has an associated current Legal ID, the ID will also be transferred to the new application. To transfer an account, without Legal ID, the Key ID, and Key Signatures can be omitted. If transferring an account with any associated Legal ID, and its corresponding private key, the Key ID and Key Signatures must be provided.

## Authentication

Requires a valid JWT bearer token.

## Notes

This endpoint uses the request schema notation described in [Pattern matching](/guides/pattern-matching).


## OpenAPI

````yaml /test-api/openapi.yaml post /Agent/Account/Transfer
openapi: 3.1.0
info:
  title: Neuron Agent API
  version: 1.0.0
  description: |-
    The Agent API exposes core Neuron functionality over HTTP so services can
    operate without a persistent XMPP connection. Endpoints are grouped by
    capability, starting with Accounts and XMPP messaging.
servers:
  - url: https://{host}
    variables:
      host:
        default: neuron.example.com
        description: Neuron domain issued to you.
security:
  - bearerAuth: []
tags:
  - name: Accounts
  - name: Crypto
  - name: Open intelligence
  - name: Legal and contracts
  - name: State machines
  - name: Storage
  - name: Tokens
  - name: Wallet
  - name: XMPP messaging
paths:
  /Agent/Account/Transfer:
    post:
      tags:
        - Accounts
      summary: Transfer
      description: >-
        Allows the client to transfer an account created using the Agent API to
        another application,  such as Neuro-Access.
      operationId: post_Agent_Account_Transfer
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                keyId:
                  type: string
                nonce:
                  type: string
                keySignature:
                  type: string
                requestSignature:
                  type: string
                pin:
                  type: string
              additionalProperties: true
              required:
                - nonce
                - requestSignature
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                properties:
                  onboardingUri:
                    type: string
                  qrCodeUrl:
                    type: string
                  qrCodeWidth:
                    type: integer
                    exclusiveMinimum: 0
                  qrCodeHeight:
                    type: integer
                    exclusiveMinimum: 0
                additionalProperties: true
                required:
                  - onboardingUri
                  - qrCodeUrl
                  - qrCodeWidth
                  - qrCodeHeight
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer

````