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).

POST /v1/powersense/analyze
{
  "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

FieldTypeDescription
okboolRequest succeeded
safeboolCurrent pattern is within healthy operating range
unsafe_probfloatEstimated abnormal state probability (0.0–1.0)
scorefloatInternal quality score
igfloatAnalysis 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).

POST /v1/maintenance/analyze
{
  "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.

POST /v1/control/optimize
{
  "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.

POST /v1/apifuzz/next-request
{
  "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.

POST /v1/distillation/analyze
{
  "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

FieldTypeDescription
topic_noveltyfloatHow novel each query topic is relative to prior queries (0–1)
structure_scorefloatStructural repetition in query patterns (0–1)
capability_depthfloatHow deep queries probe specific capabilities (0–1)
response_complexityfloatComplexity of responses elicited (0–1)
query_ratefloatNormalized query frequency (0–1)
pattern_entropyfloatEntropy of query surface features (0–1)
coverage_deltafloatRate of new capability-space coverage per query (0–1)

Response

FieldTypeDescription
distillation_probabilityfloatProbability the query pattern is distillation (0.0–1.0)
hypothesisstringlegitimate_user / systematic_distiller / evasive_distiller
confidencefloatModel confidence in the hypothesis
extraction_progressfloatEstimated fraction of capability space extracted
coverage_velocityfloatRate of capability extraction
recommended_strategystringstandard / 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

CodeMeaning
200Success
202Compute engine warming up — retry after delay (see below)
400Bad request / validation error
401Missing or invalid API key
402Quota exhausted — top up required
429Rate limit — subscription interval not elapsed
500Server 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.

Top up your account →

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 x64 macOS (coming soon) Linux (coming soon)

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

StatusMeaning
StableNOBU is not seeing a significant abnormal pattern
AttentionPattern drift or instability detected — monitor and consider servicing
RiskSignificant abnormal pattern — investigate the external power source
WarmingCompute 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
  1. Extract nobu-agent-windows.zip and run install_windows.ps1 as Administrator
  2. Edit C:\ProgramData\NobuAgent\config.yaml
  3. Set api_key, service, and backend in config.yaml
  4. 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
  1. Extract nobu-agent-macos.tar.gz and run bash install_macos.sh
  2. Edit /Library/Application Support/NobuAgent/config.yaml
  3. Add your API key

Verify: sudo launchctl list | grep com.nobu.agent

Configuration reference

FieldRequiredDescription
api_keyYesYour API key from the NOBU dashboard
serviceYespowersense or maintenance
api_urlNoAPI endpoint (defaults to production)
backendNopsutil (system metrics) or serial (RS-485/Modbus)
sample_hzNoSample rate in Hz (default: 1)
infer_intervalNoSeconds 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

PlatformFilePrerequisites
Windows x64nobu-desktop-windows-x64-v1.1.0.zipNone
macOSComing soonNone
Linux x86_64Coming soonNone

NOBU Agent (headless)

PlatformFilePrerequisites
Linuxnobu-agent-linux.tar.gzPython 3.9+
Windowsnobu-agent-windows.zipPython 3.9+
macOSnobu-agent-macos.tar.gzPython 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)