⬡ NAP V3AKL v2✦ Anthropic Claude Partner Network

Native AI Protocol
V3 Specification.

NAP V3 + AKL v2 transform your business data into cryptographically signed, AI-native endpoints — verified by Ed25519, discovered via /.well-known/ai-context, and indexed natively by GPT, Gemini, Claude, and Perplexity.

9
AI Crawlers Supported
<15m
Sync Latency
Ed25519
Signing Algorithm
99.97%
Uptime SLA

Four Layers of
AI-Native Authority

NAP V3 is not a plugin. It is a foundational infrastructure specification that makes your business data verifiable, structured, cryptographically signed, and continuously synchronized with every major AI model.

01
NAP V3 — Native AI Protocol
NAP V3 (Native AI Protocol) is the third-generation specification for exposing business data as first-class AI-readable endpoints. Every payload is structured as JSON-LD + Schema.org and delivered through a standardized /.well-known/ai-context discovery endpoint.
JSON-LD · Schema.org · /.well-known/ai-context
02
AKL v2 — AI Knowledge Layer
The AI Knowledge Layer sits between your raw business content and AI crawlers. AKL v2 normalises pricing, services, FAQs, team, and hours into a unified semantic graph that 9 major LLMs can traverse natively — without custom adapters per model.
Semantic graph · Vector-ready · Cross-model
03
EdDSA Signing + JWKS Endpoint
Every knowledge payload is signed with Ed25519 (EdDSA) asymmetric cryptography. AI crawlers and third-party verifiers can retrieve the public key set from our JWKS endpoint and independently validate the integrity and origin of your business data.
Ed25519 · X.509 · HTTPS pinning
04
/.well-known/ai-context Discovery
The ai-context well-known endpoint exposes the full machine-readable business identity in a single authenticated fetch. It follows the emerging AI Discovery standard, making your data natively indexable by GPT, Gemini, Claude, Perplexity, and every major LLM crawler.
RFC 8615 · AI Discovery · LLM-native

Public discovery
endpoints.

CatyAI's own infrastructure implements the full NAP V3 spec. Both endpoints are live, publicly accessible, and signed with our Ed25519 key pair. Use them to verify the protocol works before deploying for your business.

  • ai-context returns full JSON-LD business identity
  • jwks.json exposes the Ed25519 public key for verification
  • Both endpoints are RFC 8615 well-known compliant
  • Signed payloads verifiable by any JOSE-compliant client
  • Zero authentication required for public discovery
/.well-known/ai-context
Live machine-readable business identity endpoint
/.well-known/jwks.json
Public key set for EdDSA signature verification
Verify EdDSA signature
# Fetch public key set curl https://api.catyai.io/.well-known/jwks.json # Fetch signed ai-context payload curl https://api.catyai.io/.well-known/ai-context # Verify with jose CLI jose verify --jwks jwks.json payload.json

Your business,
native to every AI.

Join 3,000+ businesses already verified on the NAP Protocol. 14-day free trial, no credit card required.