DAH-2587: document agent-native signup in the lium skill - #3
Conversation
| ```bash | ||
| lium signup --email ada@example.com # creates the account, stores the API key | ||
| lium ls # browse machines | ||
| lium up <node-id> # rent |
There was a problem hiding this comment.
NIT: lium up prompts without -y, so this cold start stalls at the last step for a headless agent.
There was a problem hiding this comment.
Already covered — the cold-start block reads lium up <node-id> -y, so it does not prompt.
| The key is written to `~/.lium/config.ini`, so the account is then indistinguishable from one | ||
| set up with `lium init`. | ||
|
|
||
| **Requires CLI 0.0.29 or newer.** Older binaries do not have the command. Check and update: |
There was a problem hiding this comment.
NIT: main is on 0.0.28 and this PR does not bump it, so nothing pins signup to 0.0.29.
There was a problem hiding this comment.
Bumped: Datura-ai/lium#102 now sets 0.0.29 in both lium/__about__.py and pyproject.toml, so the version gate here matches what ships.
| | jq -r '.[] | select(.name=="Default") | .key') | ||
|
|
||
| lium config set api.api_key "$KEY" | ||
| lium config set ssh.key_path ~/.ssh/id_ed25519 |
There was a problem hiding this comment.
NIT: that key does not exist on a fresh host, and setting the path makes ensure_config() skip generating one, so renting fails.
There was a problem hiding this comment.
Already covered — the doc tells the agent to leave ssh.key_path unset so the CLI generates and configures the key on first use.
|
|
||
| | 403 on rent | Meaning | Action | | ||
| |---|---|---| | ||
| | `"User is not verified"` | The verification link in the welcome email has not been clicked. Only the user can click it — there is no API for it. | Ask the user to click it, then retry. Do not abandon the task. | |
There was a problem hiding this comment.
NIT: POST /auth/verify-email exists and verifies with the emailed token, so "no API for it" is not accurate.
There was a problem hiding this comment.
Fixed. The "no API for it" claim is gone; the doc now names POST /auth/resend-verify-email and POST /auth/verify-email as the recovery path, keeping "ask the user to click the link" as the primary advice.
| Funding options: | ||
|
|
||
| - Dashboard: https://lium.io/billing | ||
| - Headless invoice: `POST /tmc-pay/create-invoice` with header `X-API-Key: sk_...` returns |
There was a problem hiding this comment.
NIT: create-invoice also needs amount, crypto_currency and crypto_network in the body, otherwise it answers 422.
There was a problem hiding this comment.
Fixed — the bullet now shows the required body (amount, crypto_currency, crypto_network) and points at GET /tmc-pay/currencies for the valid pairs.
2 participants
What
Adds two sections to
lium/SKILL.md, placed right before the existinglium initauth material:POST /users,POST /users/login,GET /keys. States thatlium initis for a user who already has an account, and that the signup response carries no key.403errors fromPOST /executors/{executor_id}/rent, headless funding viaPOST /tmc-pay/create-invoice(or/nowpayments/create-invoice), and that SSH keys need no special handling.The frontmatter
descriptiongains account-creation triggers so the skill loads on "create a lium account" / "sign up for lium" phrasing.Why
Agents currently stall at the web signup form: nothing in the skill says signup is fully programmatic, so a prompt like "create a lium.io account, create an API key, rent the cheapest machine with my SSH key" dead-ends on step one. The API has been open all along — this is where that knowledge belongs.
Notes
POST /users; the section says so and is written so that update is a small edit, not a rewrite. The one-call flow is not documented as working yet.llms-full.txtis regenerated with./scripts/build-llms-full.shin the same commit; the drift check passes locally.