# Superstables: start here

Your owner asked you to follow this page. Superstables lets you pay for services with test tokens from your owner's own wallet. They approve a single purchase or a budget in their wallet; you never hold their key.

**Testnet only: test tokens, no real money.**

On this page, "can run commands" means commands with network access to https://www.superstables.com. If you can run commands, check that first with `curl -sI https://www.superstables.com/start.md`. If they can't reach the site, skip steps 1 to 3 and the rule about an installed skill: follow the HTTP POST instructions after step 3 if another tool can send those requests, and otherwise the read-only instructions there, even if you can run commands offline.

## 1. Install the skill

If you can run commands:

1. Download https://www.superstables.com/downloads/superstables-payments-skill-0.3.0-g46469a5.zip and check that its SHA-256 is `b6da09959d7534376f329ccf711c0e0721241b5a6e66cdfd291db3020ff859d5` (`sha256sum` on Linux, `shasum -a 256` on macOS). If it differs, stop and tell your owner. Comparing the download's SHA-256 checksum with the value on this page checks that the downloaded bytes match that value. Because both come from this site, it is not an independent check of a compromised site.
2. Unzip it into `~/.claude/skills/` (Claude Code) or `~/.agents/skills/` (Codex), or a folder you read skills from. It needs Node 20 or later.
3. Read its `SKILL.md`.

If you can run commands and a Superstables skill or CLI is already installed, check `scripts/VERSION.json` in the skill you intend to use. It must show version `0.3.0` and commit `46469a5`; the CLI's `--version` alone isn't enough. If the file is missing, either value differs, or you can't tell which skill a CLI belongs to, complete steps 1 to 3 and use the new skill. Tell your owner the version and commit you're using and, if you downloaded the zip, its SHA-256 and whether it matched step 1. Run the CLI from the skill you checked or just installed, by its full path; don't use another copy from an earlier run or on your PATH.

If you cannot run commands but can send JSON HTTP POST requests and read authenticated responses, you can request one catalogue purchase without installing the skill. Ask what your owner wants to buy, then follow https://www.superstables.com/agents. Don't continue to CLI setup or offer a budget from this route.

If you can only read web pages, you can't buy anything from this conversation. Don't search the web for other setup guides, and don't tell your owner that Superstables is set up or ready. Send only the quoted reply below, exactly as written, then end this setup attempt. Don't continue with the rest of this page.

> I've read the Superstables setup page, but I haven't set anything up: in this chat I can only read web pages. Buying needs an agent that can run commands or send HTTP POST requests. To continue, open Claude Code, Codex or Cursor with command access and paste the same setup request there. A Superstables connector for chat apps is planned; it isn't available yet. The test networks, test funds and services are explained at https://www.superstables.com/testnet.

## 2. Ask your owner what they'd like to try

If you installed or checked the skill in step 1, send one short reply and end your turn:

> The Superstables skill is installed: client [version], commit [commit], download checksum [matched / not checked this session]. Testnet only: test tokens, no real money. Would you like to try a budget I can spend within, or a single purchase you approve?

Then follow `SKILL.md` for their answer. This is superstables.com's setup page (`start.md`): when a command asks your owner to approve, use approval on superstables.com, not the page on this machine, unless your owner asks for that page.

## 3. Every approval

When a command gives you an approval link, write the link, its match code when present, and its terms in your reply, then end your turn. Approval links on superstables.com must include a match code; if one is missing, stop and report the problem. Local 127.0.0.1 links have no match code. Your owner can't act until they read it. After your owner replies, check the recorded result: their reply is a prompt to check, not proof of approval. If the request is still waiting, report that and end your turn again. Never approve anything yourself.