A User-Agent header is required to indicate which software is making the API requests. This helps the server better track and manage requests. A typical User-Agent might look like the following:
myapp/1.0 ([email protected]; https://example.com)

The structure serves the following purposes:

• To specify the name and version of the client (e.g., myapp/1.0).
• To provide contact information in case of issues with API usage (e.g., [email protected]).
• To optionally include a link to the documentation or website of the client (e.g., https://example.com).

Without a valid User-Agent, API requests may be rejected because the identity of the client cannot be verified, which is crucial for security and traceability. The website part is optional but recommended when relevant.

Currently, there are no rate limits enforced for this API. However, depending on future demand and usage patterns, rate limits might be introduced to ensure fairness and availability for all users.

Why a rate limit might be necessary:

• To prevent excessive usage by a single user or application, which could affect the performance for others.
• To protect the server from being overwhelmed by an unusually high number of requests.

If rate limits are implemented in the future, we will clearly communicate the limits and how they work. For now, we encourage you to use the API responsibly to avoid any disruptions.