Developers

Build on MSG through Agent APIs, CosmWasm lifecycle boundaries, canonical-role resolution, machine-readable whitepaper exports, and L1 or L2 expansion paths.

Agent API Surface Contract Runtime

Dev Tools

CLI, SDKs, automation entry points, and the whitepaper proof layer together form the current developer surface for tracing upgrades and execution boundaries.

Smart Contracts

The CosmWasm runtime now exposes wasm_migrate, reply_on or reply, and atomic rollback semantics. The public layer presents the capability direction, while the strict layer keeps the proven boundaries.

API & RPC

JSON-RPC, gRPC, REST, indexer planes, Agent APIs, and whitepaper machine-entry files define the current integration surface and now expose retention-proof / SLO / release boundaries, stricter explorer exports, and retrieval-ready references.

Deep Developer Surface

Use the whitepaper layer to inspect Agent APIs, contract lifecycle boundaries, registry or canonical-role resolution, receipts, and runtime observability together.

Agent API Registry Layer

Machine-Ready Knowledge Layer

External developers can now start from a stable `agent_entry.json`, OpenAPI summaries, topic-routing hints, module exports, chunk indexes, and dedicated indexer or explorer exports instead of scraping HTML blindly.

Agent Entry Chunk Index

Integration Kits & Demos

The whitepaper subsite also ships Telegram crawl flow, RAG ingest flow, FAQ routing templates, and minimal Python or Node demos for third-party teams.

Integration Kits Demo Clients

SDK Alpha Boundary

The whitepaper now exposes the `@msg-chain/sdk` alpha surface as a local-candidate developer layer, with explicit boundaries showing that signed public release, public distribution, and final production proof are still not closed.

SDK Surface SDK Export

Business Example Catalog

Developers and external AI agents can now inspect a machine-readable business example catalog covering payment, micropayment, registry, oracle, routing, and receipt or event samples, while the catalog still keeps a No-Go boundary for public production claims.

Business Examples Example Index

AI Quick Start

The whitepaper now exposes a short onboarding path for external AI developers, linking the developer machine pack, quick-start flow, local starter assets, and guarded release boundaries without overstating public production readiness.

Quick Start Developer Entry

Formal Contracts & Schemas

External teams can now consume a source-backed contract and API pack that points to core contract references, schema files, OpenAPI surfaces, and release-backed manifests while still keeping signed public release claims fail-closed.

Formal Contracts Core Contracts

Sandbox Strategy

The public whitepaper layer now states the current sandbox, testnet, and faucet posture explicitly: local-first, fail-closed, and not to be interpreted as a launched public testnet or public faucet claim.

Sandbox Strategy Chain Config

Web3 Contract-First Surface

Jump directly to the new Web3 protocol module for AIPAY, micropayment, trust accounting, routing registries, oracle registry, bridge adapter boundaries, and the L1 atomic-modular guardrail that keeps app state machines out of the node core.

Web3 Protocols L1 Atomic Modular