Documentation
API reference and integration guides.
Authentication
All requests require your API key in the header:
X-API-Key: nobu_your_api_key_here
Keys are issued after payment. Dashboard services use the same key.
PowerSense API From $99/month (agent) or $15/hour (API)
Power quality monitoring. Two access modes: agent+dashboard (subscription, rate-limited to your tier) or direct API (usage-metered, unlimited rate).
{
"device_id": "factory_main",
"evidence": {
"schema_id": "powersense_v1",
"channels": ["vrms", "freq", "thd"],
"series": [
{"t_ms": 0, "v": [228.5, 49.92, 0.04]},
{"t_ms": 1000, "v": [227.8, 49.88, 0.05]}
]
}
}
Response
| Field | Type | Description |
|---|---|---|
ok | bool | Request succeeded |
safe | bool | Current pattern is within healthy operating range |
unsafe_prob | float | Estimated abnormal state probability (0.0–1.0) |
score | float | Internal quality score |
ig | float | Analysis confidence delta for this cycle |
NOBU Desktop translates these fields into user-facing verdicts (Stable / Attention / Risk) and plain-language recommendations.
Predictive Maintenance API From $149/month per asset (agent) or $15/hour (API)
Equipment failure prediction. Agent+dashboard (subscription, rate-limited) or direct API (usage-metered, unlimited rate).
{
"asset_id": "pump_north_1",
"evidence": {
"schema_id": "maintenance_v1",
"channels": ["vibration", "temp", "current"],
"series": [
{"t_ms": 0, "v": [0.12, 45.2, 12.5]},
{"t_ms": 1000, "v": [0.14, 45.3, 12.6]}
]
}
}
Control API $15/hour
Optimal control for vehicles, robots, industrial systems.
{
"observed": {
"pos": 1.2,
"vel": 0.5,
"mode": 0.8
}
}
Response
{
"request_id": "req_xyz789",
"meter": {"remaining_seconds": 3540},
"action": {
"u": [0.15, -0.02],
"score": 0.87
}
}
API Fuzzing $15/hour
Security testing that finds hidden states.
{
"target_base_url": "https://api.example.com",
"observed_responses": [
{"method": "GET", "path": "/users", "status": 200},
{"method": "POST", "path": "/users", "status": 401}
]
}
Anti-Distillation API $15/hour
Model distillation detection. Identifies systematic extraction of model capabilities from API query patterns. Detects both overt and evasive distillation attempts from API query patterns.
{
"asset_id": "gpt4-production",
"topic_novelty": 0.3,
"structure_score": 0.7,
"capability_depth": 0.8,
"response_complexity": 0.6,
"query_rate": 0.9,
"pattern_entropy": 0.2,
"coverage_delta": 0.85
}
Observation fields
| Field | Type | Description |
|---|---|---|
topic_novelty | float | How novel each query topic is relative to prior queries (0–1) |
structure_score | float | Structural repetition in query patterns (0–1) |
capability_depth | float | How deep queries probe specific capabilities (0–1) |
response_complexity | float | Complexity of responses elicited (0–1) |
query_rate | float | Normalized query frequency (0–1) |
pattern_entropy | float | Entropy of query surface features (0–1) |
coverage_delta | float | Rate of new capability-space coverage per query (0–1) |
Response
| Field | Type | Description |
|---|---|---|
distillation_probability | float | Probability the query pattern is distillation (0.0–1.0) |
hypothesis | string | legitimate_user / systematic_distiller / evasive_distiller |
confidence | float | Model confidence in the hypothesis |
extraction_progress | float | Estimated fraction of capability space extracted |
coverage_velocity | float | Rate of capability extraction |
recommended_strategy | string | standard / reduced_info / adversarial |
Stateful per asset_id: consecutive calls for the same asset accumulate evidence. Converges to 99%+ confidence within 5–8 observations for systematic distillers.
Errors
| Code | Meaning |
|---|---|
200 | Success |
202 | Compute engine warming up — retry after delay (see below) |
400 | Bad request / validation error |
401 | Missing or invalid API key |
402 | Quota exhausted — top up required |
429 | Rate limit — subscription interval not elapsed |
500 | Server error |
Cold Start Handling (202)
NOBU uses on-demand compute to minimize costs. If the compute engine is stopped, the first request returns 202 Accepted with a Retry-After: 5 header. The engine boots in 60–90 seconds. Your client should retry until it receives a 200.
// Check readiness or trigger warm-up:
GET /v1/compute/status
X-API-Key: your_key
// Response (warming):
// HTTP 202 { "ready": false, "state": "pending", "retry_after": 5 }
// Response (ready):
// HTTP 200 { "ready": true, "state": "running" }
You can call GET /v1/compute/status on startup to pre-warm the engine before submitting work. No billing is consumed for warm-up calls.
Billing
Agent + Dashboard (PowerSense, Maintenance subscriptions): Flat monthly rate. Inference calls are rate-limited to your tier's interval (5 minutes for Standard, 1 minute for Professional). No compute seconds are deducted. Access expires at end of billing period.
Direct API (PowerSense API, Maintenance API, Control, Fuzzing): Metered by compute time at $15/hour. No rate limit — call as fast as you want. Each response includes remaining balance. When exhausted, requests return 402. Subscription keys that exceed their rate limit receive 429 with a Retry-After header.
NOBU Desktop v1.1.0
Cross-platform desktop app for live host metrics and periodic NOBU cloud analysis. One file, zero prerequisites.
- Compact widget with live system metrics
- Expanded dashboard with verdict history and recommendations
- PowerSense Host Telemetry Mode
- Predictive Maintenance Host Telemetry Mode
- Local 7-day and 30-day power quality summaries
Windows: single-file exe, no prerequisites, double-click to launch. macOS and Linux one-click executables coming soon. In the meantime, download the NOBU Agent (below) which runs on all platforms with Python 3.9+.
PowerSense Host Telemetry Mode
Uses local device telemetry plus NOBU cloud analysis to provide power source guidance for this PC context. Supports three advisory verdicts: continue current power source, external source may need attention, and weekly/monthly cumulative assessment.
Predictive Maintenance Host Telemetry Mode
Requires supported external vibration, pressure, and current sensors connected via USB data acquisition hardware. Without these sensor inputs, predictive maintenance inference is not available. Live host metrics remain visible.
Desktop behavior
Live local metrics update continuously on the device (every ~1 second). NOBU cloud analysis refreshes at your plan interval: every 5 minutes (Standard) or every 1 minute (Professional).
Startup behavior
If compute is cold, the first analysis may briefly show “Warming up.” The desktop app retries automatically. You can pre-warm compute via GET /v1/compute/status.
Desktop verdicts
| Status | Meaning |
|---|---|
| Stable | NOBU is not seeing a significant abnormal pattern |
| Attention | Pattern drift or instability detected — monitor and consider servicing |
| Risk | Significant abnormal pattern — investigate the external power source |
| Warming | Compute engine starting — verdict appears shortly |
NOBU Agent
For PowerSense and Predictive Maintenance, the headless agent handles sensor collection and efficient batching. It samples at a configurable rate (default 1 Hz) and sends inference requests at your tier's interval — every 5 minutes (Standard) or every 1 minute (Professional). For direct API access without the agent, purchase an API usage package instead.
NOBU Agent requires Python 3.9+. NOBU Desktop (above) is a single file with no prerequisites.
Linux installation
tar xzf nobu-agent-linux.tar.gz
cd nobu-agent-linux
sudo bash install_linux.sh
Check status: sudo systemctl status nobu-agent
View logs: journalctl -u nobu-agent -f
Windows installation
- Extract
nobu-agent-windows.zipand runinstall_windows.ps1as Administrator - Edit
C:\ProgramData\NobuAgent\config.yaml - Set
api_key,service, andbackendin config.yaml - If installed as a Windows service (NSSM):
nssm start NobuAgent
If installed as a Scheduled Task:Start-ScheduledTask -TaskName NobuAgent
Requires outbound HTTPS to your configured API endpoint. No inbound ports needed.
macOS installation
- Extract
nobu-agent-macos.tar.gzand runbash install_macos.sh - Edit
/Library/Application Support/NobuAgent/config.yaml - Add your API key
Verify: sudo launchctl list | grep com.nobu.agent
Configuration reference
| Field | Required | Description |
|---|---|---|
api_key | Yes | Your API key from the NOBU dashboard |
service | Yes | powersense or maintenance |
api_url | No | API endpoint (defaults to production) |
backend | No | psutil (system metrics) or serial (RS-485/Modbus) |
sample_hz | No | Sample rate in Hz (default: 1) |
infer_interval | No | Seconds between inference (Standard: 300, Professional: 60) |
Troubleshooting
PowerSense Host Telemetry Mode is based on this device's host telemetry context and NOBU analysis. It is not a stand-alone electrical certification.
Predictive Maintenance Host Telemetry Mode requires supported USB-connected vibration, pressure, and current sensors. Without these sensors, predictive maintenance inference is not available.
Downloads
NOBU Desktop v1.2.0
| Platform | File | Prerequisites |
|---|---|---|
| Windows x64 | nobu-desktop-windows-x64-v1.1.0.zip | None |
| macOS | Coming soon | None |
| Linux x86_64 | Coming soon | None |
NOBU Agent (headless)
| Platform | File | Prerequisites |
|---|---|---|
| Linux | nobu-agent-linux.tar.gz | Python 3.9+ |
| Windows | nobu-agent-windows.zip | Python 3.9+ |
| macOS | nobu-agent-macos.tar.gz | Python 3.9+ |
Release notes — v1.1.0
- Fixed Windows installer pip PATH issue
- Fixed API route to use
/v1/powersense/analyze - Fixed payload format (flat numeric JSON as backend expects)
- Added battery, temperature, disk latency collection
- Added pre-warm on startup via
GET /v1/compute/status - New: NOBU Desktop app with widget + dashboard UI
- New: PowerSense interpretation (Stable / Attention / Risk verdicts)
- New: Predictive Maintenance sensor gating with all verdict states
- New: Local 7-day and 30-day history summaries
- New: Startup-on-login toggle (Windows / macOS / Linux)
- New: Single-exe builds (zero end-user prerequisites)