Integrating into your dapps

Currently, we offer four ways for integrating Nad Name Service into your dapps:

• Query contract directly

• Using SDKs

• Using REST APIs

• NNS Adapters

Which integration method is best for you

🔍 Comparative summary

Integration Method	Control Level	Developer Effort	Speed & Latency	Flexibility	Ecosystem Fit
Query Contract Directly	High	High	Very fast (RPC)	Fully flexible	Neutral (raw)
NNS Adapters	Moderate	Very low	Fast	Moderate (ENS‑aligned)	Best for ENS-based tools
NNS SDKs	Moderate-high	Low-moderate	Fast	High	JavaScript-heavy dApps
REST APIs	Medium	Low	Moderate	Moderate	Backend / external service

🤔 Decision Matrix

Higher score = Better

Factor	Query Contract	NNS Adapters	SDKs	REST APIs
Implementation Speed
Customization
Performance
Decentralization
Maintenance Effort
Learning Curve

🧠 Best choice based on your needs

• You want maximum control with no dependencies? Or you are developing smart contracts → Use Direct Contract Queries

• Already using ENS tooling and library and want quick adapter support? → NNS Adapters will let you reuse existing code with minimal changes

• You're building a high‑performance frontend dApp with JS frameworks? → NNS SDKs strike a solid balance between control, speed, and ease-of-use.

• Working server-side or need simple HTTP integration? Or you just simply want to display .nad names → REST APIs offer minimal setup and broad compatibility.