enumeray access request

Request permission to run a model using request-based access.

Use when: You can discover a model but the author must review your access before execution.

Role and prerequisites: Authenticated account able to discover or address the model, with models:read for discovery and runs:create for its own request. Existing execution access is unnecessary; approval is the requested outcome. Install enumeray, configure the API and log in. Use an account or delegated token with the required permissions. Example IDs must be replaced with IDs from your service.

Example

enumeray access request scalar-double --message 'Please enable the evaluation study'

Inputs and options

Input	Meaning and use
<MODEL>	Stable model ID from model list/get or supplied by the author. An unlisted model can be addressed by ID, but still requires access.
--message <MESSAGE>	Optional human-readable explanation attached to an access request. It is visible to the model administrators.

Every command also accepts the profile, API, JSON and timeout options.

Result and next step

Creates or returns your access request; it does not grant immediate run access.

Retain the returned request ID; wait for approval or withdraw with access decide.

Exact syntax, defaults and accepted values

Request access to a model, optionally explaining the intended use

Usage: enumeray access request [OPTIONS] <MODEL>

Arguments:
  <MODEL>  Stable model ID from model list/get or supplied by its author

Options:
      --api <API>          User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --message <MESSAGE>  Optional explanation shown to model administrators; defaults to empty [default: ""]
      --profile <PROFILE>  Named local user API/login profile; host/runner commands use explicit configuration [default: default]
      --config <CONFIG>    Private user profiles file; defaults to $XDG_CONFIG_HOME/enumeray/profiles.json or ~/.config/enumeray/profiles.json
      --json               Emit user API results as JSON (NDJSON for following logs) and runtime errors on stderr; host/runner output follows its own protocol
      --timeout <TIMEOUT>  User API HTTP timeout in seconds; live logs use it for read inactivity. Does not limit execution time [default: 60]
  -h, --help               Print help