---
name: tilion
description: Use Tilion, the person's cloud browser, to open web pages, read them as markdown, collect data from a page, or reach sites that block ordinary automation. Use it when a task needs a real browser or a page that other tools cannot read.
---
# Tilion
Tilion is already set up for this person. This file tells a new session how to use it. It holds no
secret.
## Check the key
The key is `TILION_API_KEY` in the environment or the project's `.env`, or `api_key` in
`~/.config/tilion/credentials.json`. Read it in each command and never print it.
```bash
TILION_API_KEY="${TILION_API_KEY:-$(sed -n 's/.*"api_key" *: *"\([^"]*\)".*/\1/p' ~/.config/tilion/credentials.json)}"
curl -s https://back.tilion.dev/v1/usage -H "Authorization: Bearer $TILION_API_KEY"
```
- `200`: you are ready.
- `401`, or no key anywhere: Tilion is no longer set up on this machine (the key was revoked or
removed). Follow https://tilion.com/setup.md to sign in again. Ask the person for their email
address and nothing else.
If the MCP server `tilion` is in your tool list, its tools (for example `profile_list` and
`read_page`) work without any of this.
## Use it
Ask once per task, before you start a browser: say what you will open and why, and that browser time
is billed. Current rates are at `GET /v1/credits`.
```bash
# Start a browser. Billing begins. The answer holds session_id.
curl -s -X POST https://back.tilion.dev/v1/session \
-H "Authorization: Bearer $TILION_API_KEY" -H "Content-Type: application/json" -d '{}'
# Read a page as markdown.
curl -s -X POST https://back.tilion.dev/v1/extract \
-H "Authorization: Bearer $TILION_API_KEY" -H "Content-Type: application/json" \
-d '{"session_id": "<session_id>", "url": "<page>"}'
# Close it. An open browser keeps billing.
curl -s -X DELETE https://back.tilion.dev/v1/session/<session_id> \
-H "Authorization: Bearer $TILION_API_KEY"
```
Every route is listed in https://docs.tilion.dev/llms.txt.
## Habits
- Close every browser you start before you finish, because an open browser keeps billing.
- Keep the key out of messages, notes and committed files.
- For a login to another website, create a connect link (`POST /v1/credentials/connect`, or
`credential_connect` over MCP) so the person enters the login on the Tilion page.
- Ask the person before a purchase, a post or a deletion on a website.
## Disconnect
If the person asks you to disconnect, delete `~/.config/tilion/credentials.json` and this skill, and tell
them they can revoke the key under API keys in their Tilion dashboard.