> ## Documentation Index
> Fetch the complete documentation index at: https://docs.terminal3.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Start with an AI Assistant

> One prompt to paste into Claude Code, Codex or another coding assistant after you claim your key: it runs the whole Get Started guide for you.

Claimed your [API key and credits](https://docs.terminal3.io/developers/adk/get-started/prerequisites/request-test-tokens.md)? Paste the prompt below into a **new** session of Claude Code, Codex, or another coding assistant that can run commands. It follows this guide page by page: connect, create your organisation and agent, build and register the vault contract, and have your agent call it. It reports back after each step.

## Before you paste

1. **Put your key in the environment, not the chat.** The prompt never asks for it.
   * **On your own computer:** the assistant creates `my-t3n-app/.env` with an empty `T3N_API_KEY=` line. Paste your key after the `=` in your editor, save, and tell it "done".
   * **In a cloud environment** (Claude Code on the web, Codex cloud): add `T3N_API_KEY` to the environment's variables or secrets, then start a new session.
2. **Allow these hosts** if your environment restricts network access: `cn-api.sg.testnet.t3n.terminal3.io`, `docs.terminal3.io`, `github.com` and your package registries (npm, crates.io).
3. **Budget:** the full run uses about 3,000 test credits from your sign-up balance, mostly to register the contract.

## The prompt

```text theme={null}
I just claimed a Terminal 3 developer account: an API key and test credits on the T3 Network (T3N) testnet. Set me up by following the official Get Started guide from start to finish. Run the commands yourself; don't ask me to run anything.

Ground rules for this whole session:
- My API key never enters this chat. Read it only from the T3N_API_KEY environment variable or from my-t3n-app/.env (git-ignored). Never print it, ask me for it, or write it into code, git or memory. Treat AGENT_API_KEY, which you'll create later, exactly the same way.
- Testnet only.
- Follow the docs; don't improvise. They're at https://docs.terminal3.io. Add .md to any page URL for a Markdown version, and https://docs.terminal3.io/llms.txt lists every page. If a step doesn't behave as its page says, stop and tell me the exact error and which page, rather than working around it.
- Keep state in my-t3n-app/.env so a new session can carry on where this one stopped. After each step succeeds, add its marker line and skip any step already marked done. Use exactly these names: DONE_QUICKSTART, DONE_DEV_ENV, DONE_CREATE_ORG, DONE_CREATE_AGENT, DONE_FUND_AGENT, DONE_BUILD, DONE_REGISTER, DONE_STORE, DONE_GRANT, DONE_CHECK, DONE_TRY_STORE, DONE_LOG, DONE_TEST (each as NAME=1). Registering, funding and creating the organisation must never run twice.

Before anything else:
a. Check for Node.js 22 or newer and git. Make sure Rust (rustup and cargo) is installed and the wasm32-wasip2 target is added.
b. Check these hosts are reachable: cn-api.sg.testnet.t3n.terminal3.io, docs.terminal3.io, github.com, registry.npmjs.org. If one isn't, stop and tell me which host to allow in my environment's network settings.
c. Create my-t3n-app/.env if it doesn't exist, and a my-t3n-app/.gitignore that lists .env and agent-output.tmp. Then check whether T3N_API_KEY is set, in the environment or in my-t3n-app/.env, and tell me only "set" or "not set". If it's not set: add an empty T3N_API_KEY= line to my-t3n-app/.env and stop. Tell me to paste my key after the = in my editor (or, in a cloud environment, add T3N_API_KEY in the environment settings and start a new session).

Then work through these pages in order. Build one file, my-t3n-app/quickstart.ts, by appending each page's code blocks as the page says, and run it with: npx tsx --env-file=.env quickstart.ts, adding the flag the page gives for that step.
1. https://docs.terminal3.io/developers/adk/get-started/quickstart (the "I'll write the code myself" tab). Tell me the did:t3n:… it signed in as.
2. https://docs.terminal3.io/developers/adk/get-started/prerequisites/set-up-dev-env
3. https://docs.terminal3.io/developers/adk/get-started/create-organisation
   - Before creating anything, look in my-t3n-app/.env. If ORG_DID is there, reuse it. If not, list my organisations with (await t3n.myOrgs()).map(d => d.value) and reuse one I administer, saving it as ORG_DID in my-t3n-app/.env. Create one only if I have none: creating an organisation is not idempotent, and belonging to several breaks the activity log.
   - The run that creates the agent prints its API key. Send that run's output to my-t3n-app/agent-output.tmp (git-ignored), copy ORG_DID, AGENT_DID and AGENT_API_KEY into my-t3n-app/.env, then delete the file. Never show me AGENT_API_KEY.
   - Fund the agent with 5 credits, once, as the page says.
4. The walkthrough, in order:
   https://docs.terminal3.io/developers/adk/get-started/walkthrough/what-is-z-namespace
   https://docs.terminal3.io/developers/adk/get-started/walkthrough/write-contract (clone agent-vault-starter next to my-t3n-app)
   https://docs.terminal3.io/developers/adk/get-started/walkthrough/build-contract
   https://docs.terminal3.io/developers/adk/get-started/walkthrough/register-contract (copy the contract id the --register run prints into my-t3n-app/.env as CONTRACT_ID; it can't be looked up later)
   https://docs.terminal3.io/developers/adk/get-started/walkthrough/invoke-contract (run --store, --grant, --check, --try-store and --log, each on its own run)
   https://docs.terminal3.io/developers/adk/get-started/walkthrough/test

After each step, tell me in a line or two what happened. DIDs and contract names are fine to show; keys never.

At the end, summarise: my tenant DID, my organisation DID, my agent DID, my contract name, what the agent's check returned, and my remaining balance (formatTokens((await t3n.getBalance()).available)). The whole guide uses about 3,000 test credits.

Then suggest what I could build next on top of this setup, starting from https://docs.terminal3.io/developers/adk/use-cases/private-doc-scanner and https://docs.terminal3.io/developers/adk/use-cases/flight-booking. Don't start building until I choose.
```

## If the session stops

The assistant stops on purpose when your key is missing or a host is blocked. Fix the setting it names, start a new session, and paste the same prompt again. Everything it creates, and which steps are done, is kept in `my-t3n-app/.env`, so it carries on from where it stopped instead of creating a second organisation or registering twice.

Want the assistant to know the platform's pitfalls as well? Add the [ADK skill file](https://docs.terminal3.io/developers/adk/support/ai-coding-assistants.md) to your project before you paste.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.