enumeray connector grant available

Discover your active compute grants and their model-facing execution configuration.

Use when: You are an author choosing where to install and publish a model.

Role and prerequisites: Authenticated model author or compute grantee. 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 connector grant available

Inputs and options

Input	Meaning and use
--limit <LIMIT>	Maximum entries on one page, from 1 through 100. Omission retains API defaults: 20 for model catalogue, personal run history and artifacts; 25 for management collections; 50 for tokens, logs and events. Each invocation fetches one page.
--cursor <CURSOR>	Continuation from the preceding collection response. Omit for the first page; pass unchanged with the same filters. Human output prints a next-page command. Logs/events also expose a separate resume cursor for later polling; expired cursors require explicit recovery.

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

Result and next step

Returns your active grants, context IDs and disclosed execution destination. It does not grant new compute access.

Choose a context for execution.context_id in publication.json; request a grant from its connector owner if none is suitable.

Exact syntax, defaults and accepted values

Discover the compute grants available to your authenticated account

Usage: enumeray connector grant available [OPTIONS]

Options:
      --api <API>          User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --limit <LIMIT>      Maximum entries on this page (1–100); omit for the API default
      --cursor <CURSOR>    Continuation from the preceding page; pass unchanged with the same filters
      --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