# hazBase Docs

> Build RWA applications with hazBase APIs and SDKs. Explore asset and rights workflows, working samples, reference documentation and MCP integration.

## Start here
- [What you can build](/evaluate/): capabilities, applications, products, integration options and costs.
- [Quickstart](/start/day0/): configure and run the equipment, inventory or membership sample application.
- [MCP integration](/mcp/): connect your AI to documentation, SDK reference and sample operations over stdio.
- [First API request](/start/quickstart/): read public token data with @hazbase/kit@0.9.0.

## Machine-readable sources
- [Full documentation text](/llms-full.txt): Japanese and English guides, design examples and API references.
- [SDK reference JSON](/reference/sdk-contract.json): public declarations and wallet HTTP metadata, including versions and source commits.
- [Sample application and MCP server](/downloads/hazbase-day0-kit.tar.gz): application source, setup instructions, dependencies and bundled reference.

## Implementation references
- [SDK packages](/reference/sdk/)
- [Wallet HTTP API](/reference/http/)
- [Use-case patterns](/patterns/)
- [Deployment and operations](/guides/production/)

## Sample environment
The sample runs hazBase token contracts on an ephemeral local EVM (chain ID 31337). Asset metadata and operating notes are application records. Restarting resets the data; export it before stopping. The sample does not confer legal ownership, move real money or deploy to a public chain. Production integration requires contractual rights mapping, permissions, durable storage and environment-specific configuration.

## MCP connection
The distributed MCP server runs on the user's computer over stdio. It provides documentation and sample-environment operations; it does not connect to production issuance or transfer services. Configure it with the generated command and args. This website is not a remote MCP endpoint. Reference data is bundled with the server.

## Reference versions
Each SDK entry identifies its package version and source revision. Check compatibility with the installed package and API environment. The reference describes the source interface; it does not establish execution coverage for every method or business scenario.