Skip to main content
Your AI assistant usually handles requests for you. These limits matter when asking it to fetch many projects or building your own MCP client.

​
Request rate

Both limits apply. Discovery requests such as tools/list also count, so one chat message can use several requests. Creating another token for the same user and workspace does not increase the authenticated allowance. OAuth sign-in and token endpoints have separate limits. If a limit is reached, Nimt returns HTTP 429 with a Retry-After header. Wait at least that many seconds before retrying. Avoid rapid retries or repeatedly reconnecting. For large inventories, use pagination and reduce parallel requests. ChatGPT, Claude, and other clients also apply their own subscription and usage limits.

​
Page size and request size

  • Paginated tools use one-based page and bounded pageSize inputs. Project listing defaults to 25 items and accepts up to 100; analytics tools may have smaller tool-specific maximums.
  • Request bodies are limited to 128 KiB, including the JSON-RPC envelope. Send only inputs accepted by the tool’s current schema.
  • Brand override batches accept up to 100 entries, but must also fit the 128 KiB request limit. Each batch is atomic independently; splitting a job does not make all its calls one transaction.
  • The server expects uncompressed JSON over Streamable HTTP. It does not expose a local stdio server or a standalone SSE endpoint.

​
Pagination

If a project list appears incomplete, ask your assistant to fetch every page. An empty result can simply mean no projects match the search. For a custom client, keep the same filters and page size, increment page, and stop when meta.hasNextPage is false or a page is empty. Projects are currently listed newest first. Use stable IDs, not list positions, to identify records. Results are live. Projects created or deleted during pagination can change page positions and totals. Deduplicate by project ID and repeat the collection if you need a consistent comparison.

​
Timeouts and retries

Nimt allows up to 50 seconds for an MCP request. Your client may have a shorter timeout. If a request is interrupted, the next step depends on whether it was reading data or making a change.
  • Reading data: wait briefly, then try a smaller request or fewer requests at once.
  • Making a change: check the project or creation status first. A timed-out request may have completed. Repeating actions such as creating a project, replacing a prompt, generating prompts, or activating a project can cause duplicate or unintended changes.
For a custom client, retry temporary network failures and 429 responses with limited attempts and increasing delays, and only automatically repeat tools marked as read-only or idempotent (safe to repeat). Reauthenticate for expired credentials and correct invalid inputs or missing permissions before retrying. See available tools for supported capabilities and troubleshooting for what to include in a support request.