> ## 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. # Clear your custom TraderCode (deprecated PitPass path) > Clear your custom TraderCode handle. Revert the authenticated caller to their wallet-derived default, releasing the freed handle into cooldown. A no-op (returns the current default) when no custom handle is set. Like an edit, a clear counts against the rolling-hour rate-limit. Gated by the `custom_trader_codes_enabled` feature flag. ## OpenAPI ````yaml /proto-openapi/api/openapi.yaml delete /api/v1/pitpass/codes/me/custom 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/pitpass/codes/me/custom: delete: tags: - TraderCodeService - PitPass summary: Clear your custom TraderCode (deprecated PitPass path) description: |- Clear your custom TraderCode handle. Revert the authenticated caller to their wallet-derived default, releasing the freed handle into cooldown. A no-op (returns the current default) when no custom handle is set. Like an edit, a clear counts against the rolling-hour rate-limit. Gated by the `custom_trader_codes_enabled` feature flag. operationId: pitpass_clear_trader_code responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/TraderCodeResponse' '401': description: Authentication required '403': description: Custom trader codes are not enabled '429': description: Edit rate-limit exceeded '500': description: Internal server error deprecated: true security: - monacoSignature: [] - monacoHttpSignature: [] components: schemas: TraderCodeResponse: type: object properties: code: example: '0x0000000000000000000000000000000000000002' type: string description: >- Your TraderCode — your normalized wallet address (clients render it `Monaco -
`). Always present; the permanent reward identity and a public alias even when a custom handle is set. nullable: true createdAt: example: '2026-07-07T18:00:00Z' type: string description: RFC 3339 timestamp when the code row was first derived nullable: true customCode: example: CryptoKing type: string description: >- Your custom vanity handle, exactly as entered (case preserved), or an empty string when the wallet-derived default is kept. Use `is_custom` to disambiguate. nullable: true isCustom: example: true type: boolean description: >- True when a custom handle is set; false when the wallet-derived default is in effect. nullable: true display: example: CryptoKing type: string description: >- The single human-facing string to render: the custom handle when set, otherwise the `Monaco -
` default form. 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 ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.