> ## Documentation Index > Fetch the complete documentation index at: https://docs.0xmonaco.com/llms.txt > Use this file to discover all available pages before exploring further. # Register as a lead trader or edit your profile > Register as a lead trader or edit your profile. A registration is checked against the platform's eligibility rules: account equity, trading history, closed positions, and a claimed custom TraderCode handle. The profile is replaced as sent: an omitted `bio` or `minAllocation` clears it and an omitted `status` means ACTIVE; an omitted `shareBps` keeps the current share (the platform default on a registration). A follower with a live follow cannot register. ## OpenAPI ````yaml /proto-openapi/api/openapi.yaml put /api/v1/copy-trading/leaders/me openapi: 3.0.3 info: title: Monaco Protocol API description: REST API for the Monaco Protocol hybrid CLOB exchange. version: 1.0.0 servers: - url: https://staging.apimonaco.xyz description: Staging server (Testnet) security: [] tags: - name: AccountsService - name: ApplicationsService - name: AuthService - name: BuildercodeRewardsService - name: CopyTradingService - name: DelegatedAgentsService - name: FaucetService - name: FeesService - name: HealthService - name: ManagedMarketsService description: |- Wallet-authenticated maker assignments. The signed session must match both configured maker user and application. Owner IDs are process fences, never auth. Only wallet sessions are supported; delegated-agent sessions receive 403. - name: MarginAccountsService description: |- Current public isolated-margin semantics: - a user has one parent margin account per application scope - opening orders create or reuse isolated position buckets under that parent - parent account creation is handled internally by margin workflows - name: MarketService - name: OrderbookService - name: OrdersService - name: PositionsService description: |- Current public isolated-margin semantics: - positions link to a parent margin account and, when applicable, a bucket id - opening orders create or reuse isolated position buckets under the parent - users can open another isolated position by reusing the parent account with a different market bucket - name: PulseService - name: SweeperService - name: TraderCodeService - name: TradesService - name: WhitelistService - name: WithdrawalsService paths: /api/v1/copy-trading/leaders/me: put: tags: - CopyTradingService - Copy Trading summary: Register as a lead trader or edit your profile description: |- Register as a lead trader or edit your profile. A registration is checked against the platform's eligibility rules: account equity, trading history, closed positions, and a claimed custom TraderCode handle. The profile is replaced as sent: an omitted `bio` or `minAllocation` clears it and an omitted `status` means ACTIVE; an omitted `shareBps` keeps the current share (the platform default on a registration). A follower with a live follow cannot register. operationId: upsert_lead_trader requestBody: content: application/json: schema: $ref: '#/components/schemas/UpsertLeadTraderRequest' required: true responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/UpsertLeadTraderResponse' '400': description: >- Invalid request, or refused by an eligibility rule such as one lead profile per wallet (the message names the rule) '401': description: Authentication required '403': description: Delegated agent or sub-account sessions cannot register '409': description: Copy trading is not available '500': description: Internal server error '503': description: Matching engine unavailable; retry security: - monacoSignature: [] - monacoHttpSignature: [] components: schemas: UpsertLeadTraderRequest: type: object properties: shareBps: example: 1000 maximum: 10000 type: integer description: >- Profit share in basis points, within the platform's range; omitted keeps the current share (the platform default on a registration) format: uint32 nullable: true bio: maxLength: 2000 type: string description: >- Free-text profile description, at most 2,000 bytes; omitted clears it nullable: true status: example: ACTIVE type: string description: ACTIVE (default) or PAUSED nullable: true minAllocation: example: '1000' type: string description: >- Minimum follow allocation in quote units, at or above the platform floor; omitted clears it nullable: true UpsertLeadTraderResponse: type: object properties: created: type: boolean description: >- True when this call registered you, false when it edited your profile nullable: true status: example: ACTIVE type: string description: Your status after the call nullable: true shareBps: example: 1000 type: integer description: Your profit share after the call, in basis points format: uint32 nullable: true securitySchemes: monacoSignature: type: apiKey description: >- Ed25519 session-key request signing. Every authenticated request carries three headers: `X-Monaco-PublicKey` (64-char lowercase-hex session public key), `X-Monaco-Timestamp` (Unix milliseconds, within 30s of server time), and `X-Monaco-Signature` (hex ed25519 signature). The signature is over `METHOD\npath?query\ntimestamp_ms\nSHA256_hex(body)`, where the body hash is the SHA-256 of the empty byte string when there is no body. Obtain the session keypair from `POST /api/v1/auth/challenge` followed by `POST /api/v1/auth/verify`. name: X-Monaco-Signature in: header monacoHttpSignature: type: apiKey description: >- RFC 9421 Ed25519 session-key request signatures. Send Signature-Input, Signature, and Content-Digest together; never combine them with X-Monaco-* credentials. The monaco signature covers @method, @path, @query, and content-digest in that order, with created (Unix seconds within 30s of server time), keyid (registered lowercase-hex session public key), and alg=ed25519 parameters. Content-Digest uses RFC 9530 sha-256 over the exact body bytes, including the empty body. Query coverage retains ordering and percent encoding. Timestamp freshness does not reject repeated identical requests; use endpoint idempotency where supported. Existing legacy signing remains supported during server-first migration; SDK RFC 9421 signing is opt-in. See https://docs.0xmonaco.com/reference/http-message-signatures for the complete profile and trust model. name: Signature in: header ````