Komoju Rate Limits
KOMOJU does not publish fixed numeric rate limits for its REST API (https://komoju.com/api/v1) in its public documentation. As a production payment gateway it applies standard abuse and fraud protections, and clients should be prepared to handle HTTP 429 (Too Many Requests) with backoff. KOMOJU does document request-safety mechanisms that interact with retries: POST requests support idempotency via the X-KOMOJU-IDEMPOTENCY header (keys valid up to 24 hours), and a request retried before its initial response has been produced returns HTTP 409.
Komoju Rate Limits is the machine-readable rate-limit profile for KOMOJU on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests, hours, and characters.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled and conflict.
Tagged areas include Payments, Payment Gateway, Japan, Rate Limiting, and Quotas.
Limits
Policies
Sources
- https://doc.komoju.com/docs/idempotent-requests
- https://doc.komoju.com/docs/errors
- https://doc.komoju.com/docs/authentication
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/komoju-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.