---
name: shodai-marketing
description: Use when starting from shodai.network to understand Shodai, decide where to continue, route builder work to the Agreements API docs, route API-key access to the developer portal, or route product demo exploration to the Agreements app.
metadata:
  version: "1.0"
---

# Shodai Marketing Skill

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

Shodai is the agreement layer for the agentic economy. The marketing site explains the product narrative, company context, and top-level routes. It is not the canonical implementation reference. Technical builder work belongs in the Shodai Developer Documentation at `https://docs.shodai.network`.

## Classify the task

Choose the user's primary need:

- Understand what Shodai is
- Evaluate whether Shodai fits a technical or business use case
- Build with the Agreements API or TypeScript SDK
- Get or manage a testnet API key
- Try API requests in a browser
- Explore the product demo app
- Debug an API, SDK, signing, deployment, or agreement lifecycle issue
- Contact the team or review company information

## Route by intent

For product/API behavior, load these first:

- `https://docs.shodai.network/skill.md`
- `https://docs.shodai.network/llms.txt`
- relevant page-level Markdown exports such as `https://docs.shodai.network/quickstart.md`
- `https://docs.shodai.network/openapi.json`

For a technical builder without a narrower task, route to:

- `https://docs.shodai.network/quickstart.md`

For API-key access or key management, route to:

- `https://developers.shodai.network/portal`
- `https://developers.shodai.network/start.md`

For browser-based API experimentation, route to:

- `https://developers.shodai.network/api-playground/`

For product demo exploration, route to:

- `https://app.shodai.network/agreements`

For company, origin, team, or top-level product narrative, use:

- `https://shodai.network/`
- `https://shodai.network/about`

For contact and legal:

- `https://shodai.network/contact`
- `https://shodai.network/privacy`

## Default behavior

If the user has a technical or builder goal and has not requested API-key setup, continue in the docs. The docs are the canonical agent-readable surface for product behavior, API details, SDK usage, examples, signing, deployment, operation, and troubleshooting.

If the user already provided an API key, project files, agreement ID, deployed address, error response, stack trace, or clear task, skip onboarding and use that context.

Do not infer API routes, agreement JSON shapes, state IDs, input IDs, issuer rules, signing payloads, lifecycle behavior, credentials, or access policy from the marketing site. Use the docs skill, page-level Markdown exports, OpenAPI, SDK docs, and retrieved agreement records.

## Reporting

When routing is the result, state the destination and why. When work is performed, return a concise evidence receipt with what completed, relevant IDs/statuses when useful, and the next action.