Getting started
First use requires two separate setups: desktop licensing and model access. An activation key authorizes a device; Newton balance or a third-party API pays for inference. The two are not interchangeable.
Before you start
- Get an installer that matches your system and processor architecture from the official download page.
- Have the Mystilink account you use for purchasing and license management, plus an activation key from the dashboard.
- Decide on model access: for Newton, sign in with your Mystilink account and confirm your balance; for BYOK, have the vendor's API key, model access, and available quota ready.
- If you plan to look at a BaZi, Zi Wei Dou Shu, or Western natal chart, gather the birth date, birth time, and birthplace. Keep an uncertain time as unknown; do not invent a moment just to finish the form.
1. Install and launch
The download page lists the currently available systems, architectures, and installer formats. On macOS, move the app into Applications after installing; on Windows, follow the installer wizard; on Linux, use the format provided on the release page. If installation fails, see Install and update.
Downloading the software is not the same as being licensed. Only get installers from the official entry points, and confirm the file matches your system.
2. Authorize the device
Sign in to the dashboard, copy an available activation key, and paste it in full during the desktop activation step. After the first successful activation the key is associated with that device. If it was already used on an old computer, handle the device binding as described in Activation and devices before activating on the new one.
Do not paste an activation key into a model API key field, and do not treat an API key as a desktop activation key.
3. Connect a model
| Access path | What you need | Where you pay |
|---|---|---|
| Newton LLM | Signed-in Mystilink account, available balance | Newton balance in your Mystilink account |
| BYOK | Third-party vendor API key, available model | The corresponding vendor |
| Local model | A running local service, correct address and model ID | Depends on the deployment; running locally consumes local resources |
Confirm the model in use in the model settings. With BYOK, test the connection first, then save the model configuration and set it as the primary model. After a successful test, use a short message with no private records to confirm that a real conversation completes.
4. Prepare a profile card and start a conversation
Open Profile cards and fill in the birth information you need. For anything involving a natal chart, reference that profile card in the conversation and state the topic and time range you want. For example: "Based on this profile card, look at this year's career theme, and list the birth information and chart basis you used first."
If you only want a tarot or six-line reading about one matter, you can state the question up front without completing birth records for those two interactions. When drawing cards or casting, follow the prompts in the conversation panel.
Pick a system in the theory selector, or use automatic mode. Choosing a theory and choosing a model are two different decisions; see Product workflow.
5. Verify, then keep asking
Check the person, date, place, and system used in the conversation before reading the interpretation. Where the time is unknown, the records do not match, or an inquiry appears, say plainly what is uncertain. You can ask the Agent to explain the chart basis, separate different assumptions, or discuss only what is currently known.
Chart calculation and interpretation are different stages; producing a chart does not mean a prediction about the future has been validated. Important decisions still need real-world information.
Know where your data goes
Profile cards and conversation files are stored in the local workspace, but with Newton or a cloud BYOK service, the context needed to complete inference is sent to that service. The full explanation is in Privacy and local data. Once records start accumulating, set up backups as described in Backup and migration.