RentAHuman Status workflow

RentAHuman Status fetches one humanization owned by the configured RentAHuman API key.

Input

The form has one humanization-id field. Empty or whitespace-only input prevents Run with:

Enter a RentAHuman humanization id.

The draft trims surrounding whitespace before constructing argv.

Exact invocation

skryba rentahuman get <HUMANIZATION_ID>

No stdin is sent; the process receives the null device. This workflow does not accept detector or rewrite controls.

Result

On exit 0, the app keeps stdout as a string and displays it in a selectable scrolling Response panel whose detail says:

RentAHuman's own JSON, verbatim.

The app does not decode status, URLs, or nested fields. That preserves the CLI envelope and remote API response even when the upstream object grows new fields.

Credential boundary

The workflow requires RENTAHUMAN_API_KEY in the launch environment or ~/.config/skryba/env. The app never reads or validates its value. Missing key, invalid id, endpoint policy, retries, and API failures all come from the CLI on stderr and are shown unchanged.