About Protocol Agents Roadmap FAQ Contact GitHub →
// Open Standard — v2.0 — Apache 2.0 — Est. February 2026

BXP

Breathe Exposure Protocol

The open universal standard for atmospheric exposure data.
No hardware required. No licensing fees. Runs on any device.
BXP is to breath exposure data what HTTP is to the web.

Read the Specification Learn More
7M
Deaths from air pollution annually
31+
Atmospheric agents tracked
0$
Cost to adopt BXP forever
1st
Universal air exposure standard
Breathe Exposure Protocol Open Standard No Hardware Required Apache 2.0 31 Atmospheric Agents Privacy First Offline First WHO Aligned GDPR Compliant Breathe Exposure Protocol Open Standard No Hardware Required Apache 2.0 31 Atmospheric Agents Privacy First Offline First
// The Problem

The world is breathing
in the dark.

Air pollution kills more people than HIV, malaria, and tuberculosis combined. The tools to fix this exist. The data infrastructure does not. Until now.

01
Fragmentation

Every device, application, and government agency stores air quality data in a different, incompatible format. A sensor in Accra cannot speak to a hospital in Nairobi. A reading in Delhi cannot contribute to a map in London. The data exists — but it cannot connect.

02
Proprietary Lock-in

The largest air quality platforms maintain closed, proprietary data ecosystems. Researchers pay thousands to access data that should be public. Governments cannot share readings across borders. Innovation is blocked by licensing walls built for profit, not for people.

03
Geographic Inequality

97% of air quality monitoring infrastructure is concentrated in wealthy nations. The populations suffering the most — in West Africa, South Asia, Southeast Asia — have the least data, the fewest tools, and the least power to hold polluters accountable.

04
No Universal Standard

HTTP gave us the web. PDF gave us documents. MP3 gave us audio. SSL gave us security. None of these required you to build hardware. Each became the foundation an entire industry was built on. Air exposure data has never had its HTTP. Until BXP.

// What is BXP

The standard
the world
was missing.

BXP is a pure software protocol standard. It defines a universal file system architecture and data format for the capture, storage, transmission, and interpretation of atmospheric exposure data.

No sensors required. No hardware required. No centralized infrastructure required. BXP runs on any phone, any device, any platform, anywhere in the world — and it costs nothing to adopt.

It unifies data from government monitoring stations, satellites, existing sensor applications, phone-native sensors, and community reports into one open, portable, verifiable standard.

Every standard has a foundation
Web pages
HTTP
Documents
PDF
Audio
MP3
Encryption
SSL
Medical imaging
DICOM
Breath exposure
BXP ✦
// The Protocol

Five stages.
One complete system.

BXP defines a complete lifecycle for air exposure data — from the moment a reading is captured to the moment a community is protected.

01
Stage One
Locate

Every BXP record is geographically anchored using the Geohash coordinate system. Minimum precision 5 (~4.9km cell). Recommended precision 7 (~153m). The entire planet is addressable. No location is excluded.

02
Stage Two
Detect

BXP accepts data from any source — government stations, satellites, existing sensor apps, phone-native sensors, or human observation. Three capability tiers ensure every reading has an appropriate quality flag. No source is excluded.

03
Stage Three
Interpret

Raw data is normalized to BXP canonical units, corrected for temperature and humidity, and passed through automated quality control. The result is clean, comparable, trustworthy data regardless of source.

04
Stage Four
Protect

Technical measurements are translated into the BXP risk framework — six levels from CLEAN to HAZARDOUS, with specific protective actions for each. The BXP_HRI composite index incorporates all available agents for a complete picture of risk.

05
Stage Five
Report

Individual observations become collective intelligence. Community reports combine human observation with sensor data — smoke color, odor type, physical symptoms, event tags, photo evidence. One person's reading. A million people's map.

// Agent Coverage

31 agents.
Every threat.
One standard.

BXP v2.0 covers every major atmospheric threat to human health — from microscopic fine particulates to invisible carcinogenic gases to biological agents that conventional monitors ignore entirely.

🌫️
Particulates
4 agents
  • PM1
  • PM2.5
  • PM10
  • Black Carbon
💨
Gases
8 agents
  • CO
  • CO₂
  • NO₂
  • NO
  • SO₂
  • O₃
  • H₂S
  • NH₃
⚗️
Volatile Organics
6 agents
  • TVOC
  • Benzene
  • Formaldehyde
  • Toluene
  • Xylene
  • Naphthalene
🦠
Biological
5 agents
  • Mold Spores
  • Grass Pollen
  • Tree Pollen
  • Total Bacteria
  • Dust Mite
⚠️
Heavy Metals
3 agents
  • Lead (Pb)
  • Mercury (Hg)
  • Arsenic (As)
🌡️
Environmental + Derived
6 agents
  • Temperature
  • Humidity
  • Pressure
  • UV Index
  • AQI_US
  • BXP_HRI
// Why Software Only

No hardware.
No limits.

Every great standard in history succeeded because it removed the barrier of hardware dependency. BXP follows the same principle. The format is the invention — not the device.

Any existing data source can write BXP-formatted data immediately. The entire installed base of air quality infrastructure in the world becomes BXP-compatible the moment its developers adopt the standard.

Without BXP
With BXP
Incompatible formats
One universal format
Proprietary lock-in
Open forever
Hardware required
Any device, any source
Data silos
Global interoperability
No standard quality flags
Universal QC framework
Geographic exclusion
Planet-scale coverage
Compatible Data Sources
🛰️
Satellite Atmospheric Data
NASA, ESA, NOAA feeds write directly to BXP format
Tier 2
🏛️
Government Monitoring Stations
National EPA networks — export in BXP standard
Tier 3
📱
Phone-Native Sensors
Temperature, humidity, pressure, camera, GPS
Tier 1
🌐
Existing Sensor Apps
IQAir, PurpleAir, OpenAQ — BXP-compatible exports
Tier 2
👥
Community Human Reports
Observations, symptoms, event tags, photo evidence
Tier 1
🏥
Health System Records
Hospital environmental data — maps to HL7 FHIR
Tier 3
// Risk Framework

Six levels.
Universal language.

BXP defines a standardized risk communication framework that translates any combination of technical measurements into clear, actionable guidance — in any language, for any population, anywhere on Earth.

Level
BXP_HRI
AQI Equiv
General Population
Sensitive Groups
CLEAN
0–20
0–50
No restrictions. Ideal for all outdoor activity.
No restrictions.
MODERATE
21–40
51–100
Acceptable for most people.
Limit prolonged heavy exertion.
ELEVATED
41–60
101–150
Reduce heavy outdoor exertion.
Avoid outdoor exertion. Consider N95.
HIGH
61–75
151–200
Wear N95 outdoors. Close windows.
Avoid outdoors. Run air purifier.
VERY HIGH
76–90
201–300
Avoid all outdoor activity. N95 mandatory.
Stay indoors. Seek help if symptomatic.
HAZARDOUS
91–100
301–500
Emergency. Stay indoors. Do not open windows.
Evacuate to cleaner air if possible.
// Security & Privacy

Built for a world
that doesn't trust
easily.

Your exposure data is your health data. BXP treats it with the same seriousness as medical records — encrypted, private, yours to delete at any moment.

🔐
Encryption at Rest

Personal exposure records encrypted by default. Your data cannot be read by anyone — including the server hosting it — without your credentials.

AES-256-GCM
🛡️
Transit Security

All data in motion is protected with the most current encryption standard. Older, vulnerable protocols are rejected at the connection level.

TLS 1.3 Mandatory
✍️
Cryptographic Signing

Every reading can be cryptographically signed by its source device. Signed readings cannot be forged, altered, or attributed to a different origin without detection.

Ed25519 Signatures
🕵️
Privacy by Default

Person identifiers are never stored in plain form. Only SHA-256 hashes. Location precision for personal records defaults to neighborhood-level, not street-level.

SHA-256 + k-anonymity
🗑️
Right to Erasure

Complete permanent deletion of all personal exposure records with a single API call. Deletion is cryptographically verifiable. No shadow copies. No backups. Gone.

GDPR Compliant
🌳
Volume Integrity

Every BXP volume maintains a Merkle tree of all file checksums. Any tampering — with any file, anywhere in the volume — is instantly detectable without reading all data.

Merkle Tree Verification
// Roadmap

Where we are.
Where we're going.

BXP is a living standard. Each version expands the protocol's reach while maintaining perfect backward compatibility with everything that came before.

v1.0 — Frozen
The Origin
February 15, 2026 — by Elvarin
Core concept established Exposure Event schema Container schema SHA-256 verification Python implementation User-owned data principle Offline-first architecture
v2.0 — Current
The Standard
March 2026
Full file system architecture Binary .bxp format 31-agent schema REST API specification Security framework BXP_HRI formula Community reporting layer Governance model
v2.1 — Planned
The Ecosystem
Q2 2026
Python SDK JavaScript SDK Arduino SDK ESP32 SDK React Native app BXP-STREAM extension Reference server
v3.0 — Vision
The Planet
2027
Waterborne extension Soil contamination Satellite integration AI forecasting HL7 FHIR full mapping IoT mesh protocol
// The BXP Ecosystem

The standard is free.
The ecosystem
is not.

Open standards do not prevent commercial success. They enable it. Every major standard in history — HTTP, PDF, MP3 — created billion-dollar ecosystems around a free core. BXP is designed with the same architecture.

🏆
BXP Certification

Any manufacturer, developer, or organization that wants to display official BXP compliance certification goes through the BXP Foundation. Standards certification is one of the most durable revenue models in technology history.

Revenue model: per-product certification fees
☁️
Hosted BXP Volumes

The official BXP cloud infrastructure. Organizations that need a managed, compliant BXP volume without running their own server subscribe to the BXP hosting service. Free for individuals. Paid for enterprises and governments.

Revenue model: SaaS subscription tiers
🎓
Implementation Consulting

The inventor of a standard is the world's foremost expert on it. Hospitals, governments, smart cities, and sensor manufacturers pay premium rates for implementation guidance from the source.

Revenue model: enterprise consulting contracts
🌍
Foundation Grants

WHO, the Gates Foundation, the Wellcome Trust, USAID, and the African Development Bank fund open health infrastructure that serves underserved populations. BXP is exactly this. Non-dilutive. No equity given up.

Revenue model: institutional grant funding
📊
Data Intelligence

Aggregated, anonymized atmospheric intelligence derived from the BXP network. Public health researchers, insurers, urban planners, and climate organizations pay for access to population-level exposure insights.

Revenue model: data licensing and API access
📱
Native Integration

When BXP becomes the standard — and standards this well-designed always do — phone manufacturers and OS developers will build BXP support natively. Apple Health, Google Fit, Samsung Health. That moment creates extraordinary partnership and licensing value.

Revenue model: platform partnerships and licensing
// Frequently Asked Questions

Every question.
Answered.

What exactly is BXP?+
BXP (Breathe Exposure Protocol) is an open software standard — like HTTP, PDF, or MP3 — that defines how atmospheric exposure data is structured, stored, transmitted, and interpreted. It is not a device, not an app, and not a company. It is a specification that any device, application, or organization can adopt for free.
Does BXP require any hardware?+
No. BXP is a pure software protocol. Like HTTP — which didn't require you to build networking hardware — BXP defines the data format and transmission protocol, not the physical device. Any existing data source can write BXP-formatted data: government stations, satellites, consumer sensor apps, phone-native sensors, and community human reports.
How much does it cost to use BXP?+
Zero. BXP is licensed under Apache 2.0 — one of the most permissive open source licenses in existence. You can use it, implement it, build on it, and distribute it at no cost. Forever. There are no hidden fees, no premium tiers for the specification itself, and no licensing walls. The standard is free. Commercial services built around the standard are separate and optional.
Who created BXP?+
BXP was conceived and first implemented by Elvarin on February 15, 2026. The original v1 specification established the foundational concepts: user-owned data, offline-first architecture, portable containers, and SHA-256 cryptographic verification. The v2.0 specification is the direct continuation of that original work — expanded into a complete, globally deployable standard.
What data sources are BXP compatible?+
Any data source can be BXP compatible. This includes government air quality monitoring networks, satellite atmospheric data feeds (NASA, ESA, NOAA), commercial sensor applications (IQAir, PurpleAir, OpenAQ), phone-native environmental sensors, research-grade scientific instruments, and human community observation reports. BXP defines a three-tier quality framework to accommodate all sources appropriately.
How does BXP protect privacy?+
BXP treats individual exposure data as sensitive personal health information. Personal records are encrypted with AES-256-GCM by default. Person identifiers are stored only as SHA-256 hashes — never in plain form. Personal location data defaults to neighborhood-level precision, not street-level. Community aggregates are k-anonymized (minimum 5 sources). Users can permanently delete all personal records with a single API call. The entire framework is designed for GDPR, CCPA, and equivalent compliance.
What is BXP_HRI?+
BXP_HRI (BXP Health Risk Index) is BXP's native composite health risk score on a 0–100 scale. Unlike single-pollutant indices like the US AQI, BXP_HRI incorporates all available atmospheric agents simultaneously, using WHO-derived weighting factors, exposure duration modifiers, and population vulnerability modifiers. It provides a single, comprehensive number that reflects total atmospheric health risk — not just the worst single pollutant.
How does BXP handle low-quality or unreliable data?+
Every BXP reading carries a mandatory quality flag: VALIDATED, UNVALIDATED, SUSPECT, or INVALID. Automated quality control checks run on all incoming data — range validation, spike detection, flatline detection, humidity correction, and cross-sensor consistency checks. Low-quality data is never excluded — it is labeled appropriately, allowing applications to display it with proper caveats or filter it for high-stakes use cases.
Can I build a commercial product on BXP?+
Yes. Apache 2.0 explicitly permits commercial use, modification, and distribution. You can build a commercial sensor, a paid application, a data service, or any other product that implements BXP — without paying royalties or seeking permission. The only requirements are attribution and preservation of the license notice. You cannot patent BXP derivatives and use them against the project.
How does BXP relate to existing standards like AQI?+
BXP does not replace existing standards — it unifies them. The US EPA AQI, WHO Air Quality Guidelines, HL7 FHIR, OGC SensorThings API, and OpenAQ are all supported within BXP as derived fields, compatible data formats, or explicitly mapped relationships. BXP is the layer that sits above all existing standards and makes them interoperable.
What is the BXP file system?+
The BXP file system is a logical directory structure — like a file system on a computer, but for air quality data. It defines how all BXP data is organized: /locations for geographic data, /agents for pollutant definitions, /exposures for individual and aggregate records, /devices for the device registry, /community for human reports, and more. This logical structure can be implemented on any physical storage — a local disk, cloud storage, a distributed network, or embedded flash memory.
How do I contribute to BXP?+
Visit the GitHub repository at github.com/bxpprotocol/bxp-spec. The most valuable contributions right now are: reviewing the specification for technical errors or ambiguities, building reference implementations in any programming language, writing test suites, proposing extensions via the RFC process, and implementing BXP in real air quality projects and reporting your findings. All contributions are reviewed by the Technical Steering Committee and credited in the changelog.
// Origin & Mission

Built by someone
who knows what
it costs to
breathe badly.

BXP was not born in a well-funded lab or a corporate R&D department. It was born from the observation that the most important infrastructure for human health — the data layer that tells us what we are breathing — simply did not exist.

The communities that breathe the worst air have the least data about it. The populations most at risk are the least equipped to measure, understand, or respond to their exposure. BXP exists to close that gap permanently — and to do it with a tool that costs nothing and works everywhere.

The standard is open. The mission is clear. The work has begun.

February 15, 2026
BXP v1 — The Beginning

The original Breathe Exposure Protocol specification and working Python implementation published on GitHub by Elvarin. Core concepts established: user-owned data, offline-first, SHA-256 verification, portable containers. Version 1 is permanently frozen as the origin record.

March 2026
BXP v2 — The Standard

Complete expansion into a production-ready global standard. Full file system architecture, 31-agent schema, REST API specification, security framework, BXP_HRI formula, governance model, and compatibility with every major existing air quality standard.

Q2 2026 →
The Ecosystem Begins

Reference implementations, SDKs, mobile applications, and the first BXP-compatible tools. The specification becomes software. The software becomes infrastructure. The infrastructure becomes the standard the world uses.

// Six Principles
01
Universality
Works for any source, platform, geography, and scale.
02
Interoperability
Any BXP system reads any BXP file. No exceptions.
03
Openness
No fees. No closed sections. No gatekeepers. Forever.
04
Accessibility
Implementable on basic smartphones and embedded systems.
05
Privacy-First
Personal records private by default. No surveillance permitted.
06
Extensibility
Grows without breaking what was built before it.
// Get Involved

The standard is built
by the people
who need it.

BXP is governed by the BXP Foundation — an open standards body with no commercial bias. Every developer, researcher, organization, and individual is welcome to contribute, propose changes, and help build what the world needs.

📖
Read the Spec

The complete BXP v2.0 Technical Specification is publicly available. Read it, review it, implement it. Every implementation strengthens the standard.

Read SPEC.md →
🔨
Build on BXP

Reference implementations in Python, JavaScript, Arduino, ESP32, and React Native are actively needed. Build one. Become part of the foundation the ecosystem is built on.

Start Building →
💡
Propose an RFC

Have an idea for an improvement, extension, or correction? The BXP RFC process is open to everyone. Your proposal will be reviewed by the Technical Steering Committee and the open community.

Open an Issue →
You breathe 20,000 times every day.
You almost never think about it.
Seven million people die every year
from the air they had no choice but to breathe.

The data to prevent this exists.
The infrastructure to connect it did not.

Until now.

Build on BXP.

The specification is live. The standard is open. The ecosystem starts now.

View on GitHub Read the Spec Contribute
// Contact

Let's build
this together.

Whether you are a developer wanting to implement BXP, a researcher seeking to use BXP data, a government agency exploring adoption, or an organization interested in partnership — we want to hear from you.

Who should reach out
Developers building air quality applications who want to implement BXP
Sensor manufacturers interested in BXP compliance certification
Government environmental agencies exploring BXP for national monitoring
Public health researchers seeking access to BXP-structured data
Smart city projects integrating air quality monitoring infrastructure
NGOs and foundations interested in funding BXP development
Hospitals and health systems wanting to correlate patient data with exposure records
Journalists and researchers covering air quality and environmental justice
Anyone who breathes and believes that data should be open