> ## 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. # Mint all testnet tokens > Mint all testnet tokens. Mint all available testnet tokens to the authenticated user's address. Rate limited per 24 hours, per wallet and app: the same wallet has its own quota on each app. The request is synchronous: it returns 200 only once every faucet transaction is confirmed on-chain. ## OpenAPI ````yaml /proto-openapi/api/openapi.yaml post /api/v1/faucet/mint 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/faucet/mint: post: tags: - FaucetService - Faucet summary: Mint all testnet tokens description: |- Mint all testnet tokens. Mint all available testnet tokens to the authenticated user's address. Rate limited per 24 hours, per wallet and app: the same wallet has its own quota on each app. The request is synchronous: it returns 200 only once every faucet transaction is confirmed on-chain. operationId: mint_tokens requestBody: content: application/json: schema: $ref: '#/components/schemas/MintTokensRequest' required: false responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/MintTokensResponse' '400': description: Invalid request '401': description: Authentication required '429': description: Rate limit exceeded '500': description: Internal server error '502': description: >- Faucet transactions failed or were only partially confirmed on-chain; the error details carry the minted/failed breakdown. Do not blindly retry: delivered legs consume the daily quota '503': description: >- Faucet unavailable (not configured, resolver down, or reply timed out); nothing is known to have been credited, safe to retry security: - monacoSignature: [] - monacoHttpSignature: [] components: schemas: MintTokensRequest: required: - turnstileToken type: object properties: turnstileToken: type: string description: >- Cloudflare Turnstile token proving the request came from a real client. Required on every faucet mint request. MintTokensResponse: type: object properties: minted: type: array items: $ref: '#/components/schemas/MintedToken' nullable: true failed: type: array items: $ref: '#/components/schemas/FailedMint' nullable: true remainingRequests24h: example: 4 type: integer description: Remaining faucet requests in next 24h format: uint32 nullable: true MintedToken: type: object properties: assetId: example: 123e4567-e89b-12d3-a456-426614174000 type: string description: Asset UUID format: uuid nullable: true symbol: example: USDC type: string description: Token symbol nullable: true amount: example: '10000.00' type: string description: Amount minted in token units nullable: true txHash: example: 0xabc123def456... type: string description: On-chain transaction hash nullable: true FailedMint: type: object properties: assetId: example: 123e4567-e89b-12d3-a456-426614174000 type: string description: Asset UUID format: uuid nullable: true symbol: example: WBTC type: string description: Token symbol nullable: true error: example: Mint transaction failed type: string description: Error message describing why the mint failed 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.