1. Status of this document
This text keeps the API terms separate from the privacy notice. It is a working proposal: it is not a contract, it does not record acceptance and it must not be used as a final access condition until it has been completed, reviewed and published.
[PENDING: provider identity, contact channel, contractual version, acceptance procedure and governing law.]
2. Service
Platinum Gold documents a read-only REST API with item data from The Binding of Isaac. The guide and live example show how to make requests from a server-side environment without exposing a key in the browser.
The catalogue, fields, dataset versions, limits and routes may change in line with the published API contract. The current reference is the official documentation linked from this site.
3. Access requests and credentials
- Access requests may be reviewed manually and do not guarantee that a key will be issued.
- A person or entity that receives a key must keep it confidential and must not include it in public bundles, repositories, logs or code sent to the browser.
- The key must be used only for the project and purpose stated in the request, subject to the API's limits and controls.
- If a key is exposed, it must be reported through the support channel that remains to be defined and must no longer be used.
[PENDING: decide revocation, rotation, quantitative limits, support and consequences of non-compliance.]
4. Proposed acceptable use
The final version should prohibit, at a minimum, unlawful use, attempts to bypass access controls or limits, abuse that degrades the service and deliberate exposure of credentials.
The list above is a contractual design recommendation, not a current condition. It must be adapted to the actual activity, applicable obligations and the service's monitoring capacity.
5. Data, content and intellectual property
The MIT licence for the source code does not automatically grant rights to catalogue data, names, trademarks, images, fonts or other third-party resources. The licences and attributions page keeps the known inventory and permissions that still need verification.
Anyone integrating the API must check that their use of responses, images and marks respects the applicable rights and the conditions of the original sources.
6. Availability and changes
The API and its documentation may undergo maintenance, data changes, errors or interruptions. The contractual version should describe the service levels actually offered, notice of changes and the process for suspension or termination.
[PENDING LEGAL REVIEW: warranties, liability, limitations, termination and treatment of consumer users.]
7. Contact and governing law
[PENDING: legal name, address, contact email, governing law, jurisdiction and complaint or alternative dispute-resolution mechanisms.]