> ## 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. # Get my fee tier and pair schedule > Return the caller's current fee tier, rolling 14-day volumes, and a pair's schedule. Volumes and the tier are wallet-wide: the caller's wallet total across every application. ## OpenAPI ````yaml /proto-openapi/api/openapi.yaml get /api/v1/fees/tier 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/fees/tier: get: tags: - FeesService - Fees summary: Get my fee tier and pair schedule description: >- Return the caller's current fee tier, rolling 14-day volumes, and a pair's schedule. Volumes and the tier are wallet-wide: the caller's wallet total across every application. operationId: get_my_fee_tier parameters: - name: tradingPairId in: query schema: type: string minLength: 1 format: uuid description: Trading pair identifier (UUID) responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/GetMyFeeTierResponse' '400': description: Bad request (invalid trading pair id) '401': description: Authentication required '404': description: Trading pair or fee schedule not found '429': description: >- Read rate limit exceeded — every authenticated read draws one request from the account's read budget; retry after the interval in details.retryAfter '500': description: Internal server error security: - monacoSignature: [] - monacoHttpSignature: [] components: schemas: GetMyFeeTierResponse: type: object properties: currentTierLevel: example: 2 type: integer description: >- Caller's resolved tier (1–6) from the higher of their wallet's weighted 14-day volume and any volume floor set on the wallet. A floor that is set or changed counts once it applies to the wallet's fills, usually within a minute, and likewise for an account the wallet opens in a new application; a removed or expired floor stops counting at once format: int32 nullable: true weightedVolume14d: example: '7500000' type: string description: >- Caller's weighted 14-day volume (perp + 2.5× spot), summed across every application the wallet trades through nullable: true spotVolume14d: example: '1000000' type: string description: >- Caller's rolling 14-day spot volume, summed across every application the wallet trades through nullable: true perpVolume14d: example: '5000000' type: string description: >- Caller's rolling 14-day perp volume, summed across every application the wallet trades through nullable: true volumeToNextTier: example: '17500000' type: string description: >- Additional weighted volume needed to reach the next tier, counted from the volume the current tier resolved from; omitted at tier 6 nullable: true nextTierLevel: example: 3 type: integer description: Next tier level when not already at 6 format: int32 nullable: true feeSchedule: type: array items: $ref: '#/components/schemas/FeeTierScheduleRow' description: Six-row fee schedule for the requested pair, ascending by tier nullable: true FeeTierScheduleRow: type: object properties: tierLevel: example: 1 type: integer description: Tier level 1 (lowest volume) through 6 (highest) format: int32 nullable: true minVolumeThreshold: example: '5000000' type: string description: Weighted 14-day volume floor for this tier, in quote/USD units nullable: true makerFeeBps: example: '-1.15' type: string description: Maker fee in human basis points; negative is a rebate nullable: true takerFeeBps: example: '6.5' type: string description: Taker fee in human basis points 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.