> ## 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 faucet quota and recent requests > Get faucet quota and recent requests. Returns the authenticated wallet's remaining faucet requests in the rolling 24h window, when the next request becomes available, and the 5 most recent faucet requests. Quota is per wallet and app: the same wallet has its own quota on each app, and only the calling app's requests are counted and listed, matching mint enforcement. ## OpenAPI ````yaml /proto-openapi/api/openapi.yaml get /api/v1/faucet/info 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/info: get: tags: - FaucetService - Faucet summary: Get faucet quota and recent requests description: |- Get faucet quota and recent requests. Returns the authenticated wallet's remaining faucet requests in the rolling 24h window, when the next request becomes available, and the 5 most recent faucet requests. Quota is per wallet and app: the same wallet has its own quota on each app, and only the calling app's requests are counted and listed, matching mint enforcement. operationId: get_faucet_info responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/GetFaucetInfoResponse' '401': description: Authentication required '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 '503': description: Faucet quota configuration unavailable; safe to retry security: - monacoSignature: [] - monacoHttpSignature: [] components: schemas: GetFaucetInfoResponse: type: object properties: remainingRequests24h: example: 2 type: integer description: Remaining faucet requests in the rolling 24h window format: uint32 nullable: true dailyLimit: example: 3 type: integer description: Maximum faucet requests per rolling 24h window format: uint32 nullable: true nextAvailableAt: type: string description: >- Timestamp (ISO 8601) safe to retry at or after: when the wallet's next faucet slot frees under the current daily limit, with a small safety margin. When remaining_requests_24h is 0 this is when the next mint becomes possible. Absent when no requests are in the rolling 24h window or when the daily limit is 0. Not a calendar-day reset. nullable: true recentRequests: type: array items: $ref: '#/components/schemas/FaucetRequestRecord' description: >- Up to 5 most recent faucet request groups, newest first, regardless of the 24h window. nullable: true FaucetRequestRecord: type: object properties: requestedAt: type: string description: >- Timestamp (ISO 8601) of the request, truncated to the minute (display grouping; the daily quota counts every call) nullable: true minted: type: array items: $ref: '#/components/schemas/FaucetMintRecord' nullable: true description: |- Past faucet mints grouped by clock minute for display. A group can span several endpoint calls made in the same minute; the daily quota counts each call individually. FaucetMintRecord: type: object properties: assetId: type: string description: Asset UUID nullable: true format: uuid symbol: example: USDC type: string description: Token symbol nullable: true amount: example: '1000' type: string description: Amount minted in token units nullable: true txHash: type: string description: >- On-chain transaction hash; absent when the transaction was submitted but never confirmed nullable: true description: One token minted by a past faucet request. 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.