Implementations
Software you can build with.
Explore the code you can build with today, the examples you can learn from, and the previews you can help shape.
Core implementation and SDKs
Reference implementation
Registration Authority
& Transparency Log
A Go implementation of the registration lifecycle and transparency services, with local demos and an offline verifier. Run it to understand the protocol or evaluate your own deployment.
Explore ans ↗SDK + CLI
Go
Registry and transparency clients, verification, and the ANS CLI. Check the repository’s releases and documentation for the exact supported API and verification features.
Explore ans-sdk-go ↗SDK
Rust
API clients, shared types, and verification libraries with rustls support. Check the repository’s releases and documentation for the exact supported API and verification features.
Explore ans-sdk-rust ↗SDK
Java
Registration, discovery, cryptography, and agent client modules. Check the repository’s releases and documentation for the exact supported API and verification features.
Explore ans-sdk-java ↗Integrations and examples
Verifier + gateway recipes
agentgateway
& Agent Router
ans-gateway-auth verifies ANS-6 Method B callers through Envoy’s external authorization protocol. It includes gateway recipes and end-to-end suites for agentgateway and Agent Router.
Support for other Envoy-compatible gateways depends on their configuration and request forwarding. The repository documents that coverage boundary.
Source and deployment recipes ↗Research preview
NVIDIA OpenShell
ans-openshell adds signing middleware and destination registration checks outside an agent’s sandbox, keeping its identity key out of the sandbox.
Its upstream extension contracts are previews. Destination registration checks do not implement ANS-6 binding to the actual TLS peer certificate; see the repository’s security notes.
Explore the research preview ↗SDK examples
A2A, MCP & HTTP
Use the SDK examples as starting points for adding ANS verification to protocol clients and services. Protocol compatibility still requires an application to wire in and enforce verification.
Java protocol examples ↗Rust MCP client ↗Extend the ecosystem
Bring your framework.
A framework can call an ANS SDK, API, or gateway verifier, but an integration must enforce the verification result in the request path. Adding a tool to an agent’s tool list alone does not guarantee that it will be used.
Have an adapter to share? Open an issue with the public source, installation instructions, supported ANS features, and tests that demonstrate rejected invalid requests.
Contribute an integration →