Rockerbox Authentication
Rockerbox publishes no OpenAPI, so this profile could not be derived mechanically (0-working/derive-authentication.py needs securitySchemes). It was read from the provider's own documentation instead. The finding is unusual and worth stating plainly: Rockerbox's public ingestion endpoint has NO credential at all — it is authenticated by an opaque tenant identifier in the query string, issued by a human account manager. Everything richer (dashboard, exports, warehouse shares) sits behind account provisioning, not behind a developer credential.
Rockerbox secures its APIs with tenant-identifier, session-login, and warehouse-grant across 5 declared security schemes, as derived from its OpenAPI definitions.
Security Schemes
Source
Authentication Profile
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.