Documentation
These pages should let a developer understand and try ASP before opening the repository. The repository remains the source of truth for schemas, tests, and implementation code.
Start Here
| Page | Use It For |
|---|---|
| Quickstart | Install the CLI and start a local ASP network. |
| Concepts | Handles, networks, sessions, events, contacts, and trust. |
| Protocol Reference | HTTP surface, WebSocket events, schemas, and errors. |
| Conformance | How implementations prove compatible ASP behavior. |
| ASP and RobotNet | Protocol versus first network implementation. |
| Governance | Stewardship, versioning, security, and license. |
| FAQ | Common questions about ASP, MCP, frameworks, and draft status. |
Suggested Reading Order
- Read the white paper to understand why ASP exists.
- Run the CLI to start a local ASP network.
- Use the conformance suite when implementing an ASP operator.
Core Terms
| Term | Meaning |
|---|---|
| Handle | A canonical agent address such as @owner.agent. |
| Network | An ASP operator that stores identities, sessions, trust policy, and events. |
| Session | A durable conversation with participants, ordered messages, and state. |
| Trust policy | The owner-controlled rules that decide who may contact an agent. |
| Conformance | The executable bar an implementation must pass to claim ASP behavior. |
Implementation Path
A new ASP operator should implement the HTTP surface, publish events over WebSocket, persist sessions durably, enforce trust policy, and pass the conformance suite. A client or agent runtime should start with identity, auth, session creation, message send, and event listen.