The open protocol for sovereign biological data.

BSP is a neutral, open-source standard that enables any wearable, laboratory, health platform, or AI system to exchange biological data through a shared, structured, and consent-based language — where the individual always remains the owner.

Specification · Documentation · TypeScript SDK · Python SDK · CLI · AI / MCP

Every blood test, wearable reading, genomic result, and clinical record lives in a different system — owned by a different company, locked in a different format, invisible to everything else.

The patient does not own their data. The doctor cannot read the lab's output. The AI cannot access the hospital's records. The longevity protocol cannot execute without copy-pasting PDFs.

Three structural failures drive this:

BSP is the infrastructure layer that solves all three.

BSP is a neutral open protocol — like HTTP for the web, or SMTP for email, but for biological data.

It defines a complete, interoperable standard for:

BSP does not analyze data. BSP does not make medical decisions. BSP is the transport layer. Intelligence systems like AVA operate above it.

  ┌─────────────────────────────────────────────────────────────┐
  │         INTELLIGENCE LAYER  (above the protocol)            │
  │     AVA · SVA · third-party algorithms · health apps        │
  │          not defined by BSP — consumes BSP data             │
  └────────────────────────────┬────────────────────────────────┘
                               │  reads / writes via BSP
┌──────────────────────────────▼──────────────────────────────────┐
│                      BSP PROTOCOL STACK                          │
├──────────────────────────────────────────────────────────────────┤
│                                                                  │
│  LAYER 3 — BSP-EXCHANGE                                          │
│  How data moves between systems                                  │
│  Request · Response · ConsentToken · AccessControl               │
│                                                                  │
│  LAYER 2 — BSP-DATA                                              │
│  What data contains                                              │
│  BioRecord · Biomarker Taxonomy (L1 Core → L4 Device)           │
│                                                                  │
│  LAYER 1 — BSP-IDENTITY                                          │
│  Who holds the data                                              │
│  BEO (individual) · IEO (institution) · .bsp domains            │
│                                                                  │
└──────────────────────────────────────────────────────────────────┘
  Stored on Arweave — permanent, decentralized, immutable
  BEORegistry · IEORegistry · DomainRegistry · AccessControl

BSP defines the most comprehensive open biomarker taxonomy ever codified — covering the full spectrum of measurable human biology.

Every biomarker has a standardized code: BSP-{CATEGORY}-{NUMBER} (e.g., BSP-GL-001 = Fasting Glucose).

Browse the full taxonomy → bsp-spec/spec/taxonomy/

npm install bsp-sdk

import { BEOClient, AccessManager, BioRecordBuilder, ExchangeClient } from 'bsp-sdk'

// 1. Individual creates their sovereign biological identity
const { beo, keyPair } = await new BEOClient().create({ domain: 'andre.bsp' })

// 2. Grant consent to a laboratory — granular, revocable
const token = await new AccessManager({ beo, privateKey: keyPair.privateKey })
  .grantConsent({
    ieoId: 'sunrise-lab.bsp',
    scope: {
      intents: ['SUBMIT_RECORD', 'READ_RECORDS'],
      categories: ['METABOLIC', 'HORMONAL'],
      levels: ['STANDARD'],
      period: null,
      max_records: null,
    },
  })

// 3. Lab builds and submits a signed BioRecord
const record = new BioRecordBuilder()
  .beoId(beo.beo_id)
  .biomarker('BSP-GL-001')   // Fasting glucose — L2 Standard
  .value(94).unit('mg/dL')
  .timestamp(new Date().toISOString())
  .confidence(0.99)
  .sign(labPrivateKey)
  .build()

const result = await new ExchangeClient({ ieoId: 'sunrise-lab.bsp', privateKey: labPrivateKey })
  .submit(record, token)

console.log(result.arweave_txs[0])  // Permanent, immutable record on Arweave

pip install bsp-sdk

from bsp_sdk import BioRecordBuilder, AccessManager, ExchangeClient

# Build a blood test result
record = (BioRecordBuilder()
    .beo_id("patient-beo-id")
    .biomarker("BSP-GL-001")
    .value(94).unit("mg/dL")
    .timestamp("2026-02-24T08:30:00Z")
    .confidence(0.99)
    .build())

# Submit with patient consent
token = AccessManager(ieo_id="my-lab.bsp").wait_for_approval(request_id)
result = ExchangeClient(ieo_id="my-lab.bsp").submit(record, token)
print(result["arweave_tx"])  # Permanent record

npx bspctl create andre.bsp           # Create biological identity
npx bspctl consent grant <beo> <ieo> --intents SUBMIT_RECORD --days 365
npx bspctl export <beo> --token <tok> --format FHIR_R4
npx bspctl destroy <beo> --confirm    # LGPD/GDPR erasure

Add BSP to your Claude Desktop claude_desktop_config.json:

{
  "mcpServers": {
    "bsp": {
      "command": "npx",
      "args": ["bsp-mcp"],
      "env": { "BSP_BEO_DOMAIN": "your-name.bsp" }
    }
  }
}

Then ask Claude: "What do my last blood test results say about my longevity markers?"

Developers building health apps, longevity platforms, or patient-facing tools that need interoperable biological data.

Laboratories and clinics that want to submit structured exam results with patient consent — without proprietary integrations.

Health platforms that want to become interoperable with any other BSP-compatible system in the world.

AI researchers and engineers who need structured, high-quality biological data for training, analysis, or real-time inference.

Individuals who want sovereign control over their own biological history and the ability to share it on their own terms.

BSP evolves through Biological Improvement Proposals (BIPs) — a community-driven governance process modeled after established open standards (BIPs, EIPs, RFCs).

1. Read the governance model
2. Use the BIP template
3. Open a Pull Request in bsp-spec

Protocol changes require community discussion and multi-signature approval from the Ambrósio Institute council.

For SDK contributions, see CONTRIBUTING.md in each repository.

Specification — Creative Commons Attribution 4.0 (CC BY 4.0) Anyone may implement, build on, or distribute the BSP specification without fees or permission.

SDKs — Apache License 2.0