enumeray access accept

Accept a model invitation by reading its secret token from stdin.

Use when: You are the intended recipient of an active model invitation.

Role and prerequisites: Invitation recipient. 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

jq -r .token invitation.json | enumeray access accept scalar-double

Requires jq for this example and the private invitation response file from the model administrator. A different logged-in account cannot redeem a recipient-bound invitation.

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.

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

Result and next step

Redeems the invitation for the authenticated matching recipient; the token never appears in process arguments. Reaccepting that same invitation as the same recipient returns its original acceptance even after expiry, but does not restore access revoked later.

Inspect model get and publication availability, then initialize an analysis directory.

Exact syntax, defaults and accepted values

Read an invitation token from stdin; tokens never appear in process arguments

Usage: enumeray access accept [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
      --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