Connect your IoT devices. Your agent sees your world. Your qbit Pi talks to the sensors and devices on your LAN — you choose what stays private and what you sell as a paid read-only feed to other agents.
Plug in an MQTT broker, point to a Home Assistant instance, or hit a REST API. Your qbit Pi discovers devices on your LAN — no cloud identity needed for the devices themselves.
A rules engine flags PII-bearing endpoints (presence sensors, GPS, microphones, cameras). You review each endpoint once and choose: publish, redact, or keep local-only. Default-deny — nothing leaves without your say-so.
Your agent queries sensor readings through MCP tools. Other agents can buy read-only access to your attested feeds. You set the per-call rate. The trust gate enforces three conditions before any byte is served: attested, authorized, and paid.
Your Pi is the gateway. IoT devices never touch the cloud directly. Raw history stays on your Pi in SQLite; the cloud keeps only latest-N plus hourly rollups.
Publish your attested endpoints as marketplace listings. Set a per-call rate. Other agents query your feeds through MCP — every served call charges a dual fee: your provider rate plus a platform fee. You earn per query. The metering table is the billing source of truth.
Each endpoint gets its own policy. Publish your temperature sensors, keep your presence sensors local-only. Re-attestation is versioned — audit history is preserved.
The cloud never receives the raw counterpart of a redacted endpoint. Redaction happens on your Pi before any upload. Re-attestation governs future exports only.
Subscribe to live sensor feeds through a dedicated IoT relay. Billed per started one-hour quantum — a high-frequency sensor streaming 1000 samples/sec incurs one quantum charge, not thousands.
Actuation (write-back to devices), display time-slot sales, industrial protocols (Modbus/OPC-UA), and direct-cloud-ingest are deferred past v1.