# Start From Shodai Developer Portal

Use this runbook when the user or agent starts from `https://developers.shodai.network`.

## Classify the user's goal

- Get or manage API access
- Run the docs Quickstart
- Try the API in the browser playground
- Work in an existing project
- Inspect or operate an existing agreement
- Explore the demo app product workflow
- Debug an API, auth, deployment, signing, or input issue

If the user already provided `API_KEY`, project files, an agreement ID, a deployed address, an error response, or a clear task, skip introductory onboarding and use that context.

## Route to the right source

- For product/API behavior, load `https://docs.shodai.network/skill.md`.
- For the documentation index, load `https://docs.shodai.network/llms.txt`.
- For the default first experiment, use `https://docs.shodai.network/quickstart.md`.
- For raw routes and schemas, use `https://docs.shodai.network/openapi.json`.
- For browser experimentation, use `https://developers.shodai.network/api-playground/`.
- For the product demo app, use `https://developers.shodai.network/agreements/home`.

## API access

Use an existing `API_KEY` from the environment or local project context when available.

If the user has delegated setup and browser automation is available, you may use the developer portal to obtain testnet API access. Handle credentials according to the user's environment and normal secret-handling conventions.

## Default first experiment

For a first API experiment, use the SDK-first path in the docs Quickstart:

1. Load docs context from the docs skill, `llms.txt`, relevant `.md` pages, and OpenAPI.
2. Install `@cns-labs/agreements-api-client` and `viem`.
3. Create `ApiClient` for testnet unless the user requested another environment.
4. Confirm health and authenticated list access.
5. Validate a real docs example agreement.
6. Run deployment preflight.
7. Deploy and submit an input when credentials and signing context are available.
8. Return a concise evidence receipt.