BNRP API

Returns the canonical BNRP record for a Bitcoin-native name. The resolver queries upstream indexers (UniSat, BTCName, SNS), selects the first inscription as canonical, and caches the result for 300 seconds.

GET https://api.bnrp.name/v1/resolve?name=satoshi.btc

HTTP/1.1 200 OK
Content-Type: application/json

{
  "name": "satoshi.btc",
  "inscription_id": "abc123...i0",
  "owner": "bc1p...",
  "addresses": {
    "BTC":       "bc1p...",
    "LIGHTNING": "satoshi@getalby.com",
    "ETH":       "0x...",
    "SOL":       "So1..."
  },
  "profile": {
    "avatar":       "ord:abc123...i0",
    "display":      "Satoshi",
    "description":  "Bitcoin.",
    "com.twitter":  "satoshi",
    "url":          "https://bitcoin.org"
  },
  "via": "unisat",
  "resolved_at": "2026-04-23T20:00:00Z",
  "cached": true
}

Returns all BNRP names owned by a given Bitcoin address. Cached for 120 seconds.

GET https://api.bnrp.name/v1/reverse?address=bc1p...

HTTP/1.1 200 OK
Content-Type: application/json

{
  "address": "bc1p...",
  "names": [
    "satoshi.btc",
    "punk.ord"
  ],
  "cached": false
}

Full shape of a resolved BNRP name record. All fields except name and inscription_id are optional.

{
  "name":           string,   // Full name with TLD, e.g. "satoshi.btc"
  "inscription_id": string,   // Ordinals inscription ID (txid + "i" + index)
  "owner":          string,   // Current Bitcoin owner address
  "addresses": {
    "BTC":          string,   // Primary Bitcoin address (P2TR)
    "LIGHTNING":    string,   // LNURL or Lightning address
    "ETH":          string,   // Ethereum address (optional)
    "SOL":          string    // Solana address (optional)
  },
  "profile": {
    "avatar":       string,   // "ord:{inscriptionId}" or https URL
    "display":      string,   // Display name
    "description":  string,   // Bio / description
    "com.twitter":  string,   // Twitter/X handle (without @)
    "com.github":   string,   // GitHub username
    "url":          string    // Website URL
  },
  "via":            string,   // Upstream source: "unisat" | "btcname" | "sns"
  "resolved_at":    string,   // ISO 8601 timestamp of resolution
  "cached":         boolean   // true when served from KV cache
}

Market listing data returned by the BTCNative market worker. Listings are created via UniSat's PSBT-based auction protocol and proxied through the BTC Native market worker.

{
  "ok": true,
  "listings": [
    {
      "name":        "satoshi.btc",
      "auctionId":   "abc123",
      "unitPrice":   150000,       // sats
      "inscriptionId": "abc...i0",
      "seller":      "bc1p...",
      "listedAt":    "2026-04-01T12:00:00Z"
    }
  ],
  "total": 42
}

Fee schedule for BRC-20 token trades settled through BTCNative.

How BNRP determines canonical ownership. There is no smart contract. Verification is a read of Ordinals inscription data.

Canonical rule:
  The FIRST inscription matching name + TLD is canonical.
  All subsequent inscriptions for the same name are ignored.

Ownership:
  owner = current UTXO holder of the inscription.
  Transfers follow Bitcoin UTXO rules — no protocol overhead.

Spoof detection:
  - Re-inscriptions: blocked at resolver level.
  - Unicode homoglyphs: flagged client-side by BNRP trust layer.
  - Mixed scripts: flagged as "Confusable" in name card badges.

Resolution chain:
  1. Query upstream (UniSat / BTCName / SNS)
  2. Select inscription with lowest block height (first = canonical)
  3. Verify owner address matches current UTXO holder
  4. Return normalized record with via + resolved_at
  5. Cache in Cloudflare KV for 300s

All errors return JSON with a consistent shape.

{
  "error": "name_not_found",  // Machine-readable error code
  "message": "No inscription found for this name.",
  "status": 404
}

The public resolver API has IP-based rate limiting enforced at the Cloudflare Worker edge.

Namespace endpoints return the full ownership tree, subname records, inscription history, and current record state for a name. These endpoints are part of the BNRP resolver and require no API key.

GET https://api.bnrp.name/v1/names/satoshi.btc/namespace

// Response
{
  "name": "satoshi.btc",
  "policy": "parent-controlled",
  "resolverStatus": "verified",
  "subnameCount": 0,
  "latestRecord": {
    "inscriptionId": "abc123...i0",
    "op": "profile",
    "nonce": 1,
    "confirmedAt": 840000
  }
}

GET https://api.bnrp.name/v1/names/satoshi.btc/subnames

// Subname record schema
{
  "name": "vault.satoshi.btc",
  "parent": "satoshi.btc",
  "owner": "bc1p...",
  "op": "subname_register",
  "records": {},
  "provenance": {
    "inscriptionId": "def456...i0",
    "confirmedAt": 841500,
    "nonce": 1
  },
  "status": "active"
}

GET https://api.bnrp.name/v1/names/satoshi.btc/history

// Response
{
  "name": "satoshi.btc",
  "history": [
    {
      "inscriptionId": "abc123...i0",
      "op": "profile",
      "nonce": 2,
      "confirmedAt": 842000,
      "valid": true,
      "validityState": "active"
    },
    {
      "inscriptionId": "old789...i0",
      "op": "profile",
      "nonce": 1,
      "confirmedAt": 840000,
      "valid": false,
      "validityState": "superseded"
    }
  ]
}

GET https://api.bnrp.name/v1/names/satoshi.btc/current-record

// Response
{
  "name": "satoshi.btc",
  "inscriptionId": "abc123...i0",
  "op": "profile",
  "nonce": 2,
  "owner": "bc1p...",
  "records": {
    "btc": "bc1p...",
    "com.twitter": "satoshi"
  },
  "confirmedAt": 842000,
  "validityState": "active"
}

Namespace endpoints are Phase 2 roadmap. The resolver stub is live — subname issuance is not yet active. Learn about namespaces →

Subnames

Subnames are Bitcoin-native child records created under a root name. They use the BNRP subname_register op and are indexed from Bitcoin inscriptions.

Event format

{
  "p": "bnrp",
  "op": "subname_register",
  "name": "artist.btc",       // parent name
  "sub": "shop.artist.btc",   // full subname
  "to": "bc1p...",             // primary destination
  "records": {                  // optional extended records
    "btc": "bc1p...",
    "website": "https://...",
    "lightning": "lnbc...",
    "com.twitter": "@handle"
  },
  "nonce": 1,                   // must strictly increase
  "v": 1                        // protocol version
}

Validity rules

A subname record is valid if:

• The inscription was made by the current owner of the parent name, or an approved delegate
• The nonce strictly increases from the previous record for this subname
• The record has not been revoked by a subsequent subname_revoke event
• The record conforms to the parent namespace policy
• The inscription is confirmed on-chain

Supported ops

GET /names/:name/subnames

Returns all active subnames for a given parent name.

GET https://api.bnrp.name/v1/names/artist.btc/subnames

Response:
{
  "name": "artist.btc",
  "count": 3,
  "subnames": [
    {
      "name": "shop.artist.btc",
      "records": { "btc": "bc1p...", "website": "https://..." },
      "status": "active",
      "nonce": 1
    }
  ]
}

BNRP is an open protocol. Bug reports, integration questions, and protocol proposals are welcome.