NIP-86 defines a JSON-RPC interface for relay management, letting authorized clients send administrative commands to relays over a standardized API. Relay operators can ban or allow pubkeys, manage access lists, and query relay state without relay-specific tooling.

How It Works

The management API uses JSON-RPC-like requests over HTTP on the same URI as the relay websocket endpoint. Requests use the application/nostr+json+rpc content type and authenticate with a NIP-98 (HTTP Auth) signed event in the Authorization header. The relay verifies the requesting pubkey against its admin list before executing commands.

Available methods include banning and allowing pubkeys, listing banned users, and querying relay configuration. The standardized interface means a single client implementation can manage any NIP-86-compatible relay.

A September 2026 merge added listclaims, createclaim, and deleteclaim for the NIP-43 invite codes a relay accepts. A relay operator can issue and revoke those claims through the same management interface. Support remains optional for individual relay implementations.

Implementations

  • Amethyst - Android client with NIP-86 relay management UI (v1.07.0+)

Primary sources:

Mentioned in:

See also: