Nastar documentation
Reference material for integrating the Nastar consent SDK and calling its management API — written against the actual implemented code, not aspirational endpoints. If a page describes something that isn't built yet, it says so plainly instead of describing it as working.
nastar.dev, the API on api.nastar.dev, and the SDK on cdn.nastar.dev. Two gaps are worth knowing before you start: @nastar/consent-sdk is not published to npm yet, so install it from the CDN (SDK reference), and only the plain HTML and Nuxt integration guides exist. Start with Quickstart. Where to start
- New to Nastar — start with Quickstart.
- Integrating with an AI coding assistant — start with AI IDE integration.
- Calling the API directly — start with API reference.
All guides
Quickstart
Create a site, publish a config, and install the SDK end to end.
AI IDE integration
A checklist and copyable prompts for integrating Nastar with an AI coding assistant.
SDK reference
The full @nastar/consent-sdk API — types, lifecycle, and edge-case behavior.
API reference
The management and public REST API, generated OpenAPI document, and the two auth models.
Security
How OTP auth, sessions, and setup tokens are stored and rate-limited.
Troubleshooting
Fixes for the CORS, publish, and consent-state issues integrators hit most.
Guide: plain HTML
A tested, working integration into a static site with no build step.
Guide: Nuxt
The SDK in a Nuxt app, including SPA page views — the pattern running on this site.