Status, Support, and Deprecation
Support
Every invocation returns or records a request or correlation identifier. Provide that identifier, UTC timestamp, client ID, environment, and operation key when contacting support. Exclude credentials and private payload bodies.
Service status
Use the Batoi public status and support channels linked from Developers Central. Treat repeated 5xx responses as an incident signal; use bounded retries and avoid traffic amplification.
Deprecation
A deprecation notice identifies the affected contract or compatibility address, replacement, notice date, intended sunset, and migration evidence. Deprecation does not permit a silent schema or authorization change.
Clients should inventory contract hashes and operation keys, test the replacement in sandbox, promote deliberately, and confirm the old consumer is no longer active before sunset.
The configured www API host is currently a same-runtime compatibility address for https://batoi.com/api/; no removal date is approved. Host or route compatibility is retired only after credential-free traffic evidence meets the published zero-use threshold, named consumers are cleared, compatibility tests and rollback rehearsal pass, and the owner approves the change.
Revocation
Security revocation can take effect immediately. Revoked publications and bindings fail closed even when a previously downloaded artifact still exists.