English 中文版
NPS is a multi-layer protocol suite. Where you start depends on what you’re building.
The latest suite release is 1.0.0-alpha.18, published 2026-08-15. Install
commands and SDK notes remain aligned with that release. The specification tree
contains the reviewed, unreleased alpha.19 candidate; package-manager
availability is tracked per ecosystem.
You need an SDK. Pick your language and follow the quickstart on the Wiki.
| Language | Install | Wiki quickstart |
|---|---|---|
| Python | pip install nps-lib==1.0.0a18 |
SDK-Python |
| TypeScript | npm install @labacacia/nps-sdk@1.0.0-alpha.18 |
SDK-TypeScript |
| Rust | cargo add nps-sdk@=1.0.0-alpha.18 |
SDK-Rust |
| Go | go get github.com/labacacia/NPS-sdk-go@v1.0.0-alpha.18 |
SDK-Go |
| Java | implementation("com.labacacia.nps:nps-java:1.0.0-alpha.18") |
SDK-Java |
| .NET | dotnet add package LabAcacia.NPS.Core --version 1.0.0-alpha.18 |
SDK-dotnet |
Python note: PyPI normalizes the pre-release suffix, so the suite’s
1.0.0-alpha.18is published as1.0.0a18.npm note: pin the explicit version, or use the
alphadist-tag — both resolve to1.0.0-alpha.18. The unqualifiedlatestdist-tag is deliberately still1.0.0-alpha.7, sonpm install @labacacia/nps-sdkwith no version or tag will not give you the current release.
You need the NPS Daemons bundle (npsd + nps-runner + nps-ingress + nps-registry).
nps-ingress is a process-level Internet ingress daemon name, not the retired
NWP Gateway Node logical role. CR-0001 replaced that logical role with
Anchor Node and Bridge Node.
Read the protocol specs (linked from Protocols), then pick a compat adapter:
compat/mcp-ingress — MCP → NPS translationcompat/a2a-ingress — A2A → NPS translationcompat/grpc-ingress — gRPC → NPS translation→ Wiki: Protocol-Designer-Guide
Start with Overview (5 min read), then Protocols for the five-layer architecture.
See CONTRIBUTING for the process, and Wiki: Contributors-Guide for conventions.
📖 For tutorials, references, and operator guides, see the NPS handbook.