Skip to Content
Quick start

Quick start

Connect a wallet, register a site, paste the widget, install the package, and start sending content plus unlock events to Nibgate.

The widget verifies the website. The package powers gating, payments, content metadata, unlock events, and receipt reporting.

Using an AI coding agent? Give it https://nibgate.xyz/skill.md  or node_modules/@nibgate/sdk/SKILL.md before it edits your integration.

Connect wallet

Your wallet is the creator identity. It owns the profile, connected sites, content dashboard, analytics, and earnings views.

Register your site

Add the exact origin where protected content lives, for example https://creator.com. Nibgate returns a siteId and verification token.

Only register domains you control.

Paste the widget

The widget verifies ownership and streams page activity from the verified domain.

<script async src="https://www.nibgate.xyz/widget.js" data-nibgate-site="site_..." data-nibgate-token="ngv_..." data-nibgate-api="https://api.nibgate.xyz"> </script>

Install the package

The package belongs in the creator app. It controls gating, pricing, content metadata, unlock events, and receipt reporting.

npm install @nibgate/sdk

Publish content metadata

Send public metadata for each paid resource. Keep the protected content itself on your own domain.

import { createGate } from '@nibgate/sdk' const guide = createGate({ id: 'premium-guide', title: 'Premium Guide', type: 'article', price: '0.01', path: '/premium-guide', access: { humans: 'paid', agents: 'paid' }, unlock: { mode: 'one_time' } }) guide.content() guide.view()

Check the dashboard

Use Sites, Contents, Analytics, and Earnings to confirm the setup is active.

MVP unlock model

For the first stable package, Nibgate should ship one unlock path well:

pay once -> verify receipt/proof -> issue unlock token -> serve content -> report receipt

The unlock policy field already supports metered streaming, metered reading, time passes, and agent quotas in the resource schema; their payment/session adapters are not production-ready yet, so one_time is the shipped path.

Next reads

Last updated on