# Shodai

> Top-of-funnel entrypoint for Shodai, the agreement layer for the agentic economy.

Shodai turns commitments between humans and AI agents into living agreements: workflows that encode obligations, track fulfillment, and make delivery verifiable. This site is for understanding what Shodai is. Technical builder work routes to the docs. API-key access routes to the developer portal. Product demo exploration routes to the Agreements app.

## Start here

- [Marketing skill](https://shodai.network/skill.md): Routing guidance for agents starting from shodai.network.
- [Docs skill](https://docs.shodai.network/skill.md): Canonical agent workflow for API, SDK, signing, deployment, operation, and troubleshooting tasks.
- [Docs llms.txt](https://docs.shodai.network/llms.txt): Complete documentation index.
- [Quickstart](https://docs.shodai.network/quickstart.md): Default first technical path.
- [OpenAPI](https://docs.shodai.network/openapi.json): Exact Agreements API routes, request bodies, response schemas, and servers.

## Route by user intent

- [Docs skill](https://docs.shodai.network/skill.md): Build with the Agreements API, use the SDK, author agreement JSON, sign permits, deploy agreements, submit inputs, inspect state, or debug API behavior.
- [Developer Portal](https://developers.shodai.network/portal): Get or manage API keys.
- [API Playground](https://developers.shodai.network/api-playground/): Try API requests in a browser.
- [Demo App](https://app.shodai.network/agreements): Explore the product workflow for templates, drafts, deployed agreements, signing, available actions, and agreement operation.
- [Homepage](https://shodai.network/): Understand what Shodai is and who it is for.
- [About](https://shodai.network/about): Read the origin, thesis, and team.
- [Contact](https://shodai.network/contact): Contact Shodai.
- [Privacy](https://shodai.network/privacy): Review privacy terms.

## Marketing pages

- [Homepage](https://shodai.network/): What Shodai is and who it is for.
- [About](https://shodai.network/about): Origin, thesis, and team.
- [Contact](https://shodai.network/contact): Contact Shodai.
- [Privacy](https://shodai.network/privacy): Privacy policy.

## Build and integrate

- [Docs skill](https://docs.shodai.network/skill.md): Product and API workflow guidance.
- [Docs llms.txt](https://docs.shodai.network/llms.txt): Docs-side routing index.
- [Quickstart](https://docs.shodai.network/quickstart.md): First SDK workflow end-to-end.
- [OpenAPI](https://docs.shodai.network/openapi.json): Exact routes, request/response schemas.
- [Developer portal runbook](https://developers.shodai.network/start.md): What to do when starting from the developer portal.
- [API playground](https://developers.shodai.network/api-playground/): Browser-based API experimentation.
- [Demo app](https://app.shodai.network/agreements): Walk through the live agreement workflow.

## Optional

- [Developer Portal](https://developers.shodai.network): Portal routing and access surface.
- [Portal llms.txt](https://developers.shodai.network/llms.txt): Portal-side routing index.
- [Portal skill](https://developers.shodai.network/skill.md): Portal-side routing guidance.
- [Docs home](https://docs.shodai.network): Docs landing.

## Connect agents via MCP (agent-ready API + live hosted MCP, readiness-gated)

Shodai runs a hosted Model Context Protocol server so agents can author, validate, deploy, and operate agreements as tools. The endpoint is live; broad "MCP ready" / "connect any client" is readiness-gated.

- Hosted MCP (Streamable HTTP): https://shodai.network/mcp
- Auth: `Authorization: Bearer <API key>` — keys begin `cns_pk_`, created in the developer portal; environment-scoped (testnet / production).
- Discovery card: https://shodai.network/.well-known/mcp/server-card.json
- [Connect via MCP](https://docs.shodai.network/sdks/connect-via-mcp): Full setup — client config, MCP Inspector transcript, tool schemas, safety tiers, auth scope.
- REST API (`/v0`) and a direct on-chain SDK (`@cns-labs/agreements-protocol-evm`) are also available.

What an agent can do today:

- Author, validate, and preflight an agreement — read-only, no signing.
- Deploy an agreement and submit inputs that advance its on-chain lifecycle, using EIP-712 permits you sign. Shodai never holds your keys.
- Read agreement records, current state, rendered documents, and full input history.

Agent tools (live; reads are safe to call freely, writes require your signature):

- Reads: list_agreements, get_agreement, get_agreement_document, get_agreement_state, get_input_history, validate_agreement, preflight_deployment
- Sign-prep (read-only): prepare_deployment_typed_data, prepare_input_typed_data
- Writes (require your signature): deploy_agreement, submit_input

Best first workflow:

- [Run an end-to-end agreement workflow](https://docs.shodai.network/examples/end-to-end-workflow): The recommended full lifecycle workflow — validation, deployment preflight, signing, deployment, input submission, state, and input history.
- [Quickstart with MCP](https://docs.shodai.network/sdks/quickstart-with-mcp): Hosted MCP setup, authenticated tools, typed-data signing preparation, and safety constraints.

Not yet / do not assume:

- Broad "MCP ready" or "connect any MCP client" — the hosted surface is live but readiness-gated.
- OAuth / session auth — not yet; API-key Bearer only.
- x402 agent payments — planned, not implemented.
- No legal finality and no fully autonomous enforcement: agreements track and gate verifiable inputs; they do not replace courts and do not move value without an authorized, signed input.

## Notes for agents

- If you have an API key, project, agreement ID, error response, or a clear task, skip onboarding and go directly to the docs or developer surface that fits.
- This file is not canonical for quickstart steps, API schemas, SDK instructions, key-generation, or access policy. Use the docs skill, docs page-level Markdown exports, and OpenAPI for those.