Skip to main content

v0.3 — Real-Time Intelligence Cloud

Quantinal v0.3 sharpens the product around real-time intelligence for private workspaces — your spaces, trackers, and data stay under your account.

Breaking changes

Review the Breaking changes section below before upgrading integrations. linked_trackers is restricted to your own trackers, and several response fields are no longer returned.

Overview​

  • Private workspaces — Quantinal is built for teams running their own intelligence workflows
  • Linked trackers — agent_config.linked_trackers accepts your own tracker IDs only (same space)
  • Reasoning modes — basic, advanced, super, and zen (async only) with updated cost multipliers
  • Bidirectional score threshold alerts — email and webhook alerts can fire on a lower bound, an upper bound, or both at once (e.g. score ≤ 20 or ≥ 80)

Breaking changes​

Changes below affect endpoints documented in Tracker endpoints.

Stricter linked_trackers validation​

On tracker create and update (POST/PATCH /v1/api/trackers/...):

  • agent_config.linked_trackers must contain only tracker IDs you own in the same space
  • Cross-user tracker IDs → 400 Bad Request
  • Maximum 10 linked trackers (unchanged)

Migration: Remove any linked_trackers entries that reference another user's trackers. Replace with your own tracker IDs from the same space, or omit the field.

Removed response fields​

The following fields are no longer returned on tracker payloads. Clients should not depend on them:

FieldNotes
visibilityAll trackers are private
is_publicRemoved
star_countRemoved
usage_countRemoved from tracker responses
published_atRemoved

Run execution​

  • zen reasoning mode requires async execution (sync: false). Sync requests return 400.
  • Linked tracker context uses owned trackers only in the same space.

Pricing​

  • Linked trackers are free — remove any public_tracker_cost add-on from run cost calculations.

Migration checklist​

  1. Audit linked_trackers — on each tracker, ensure every ID in agent_config.linked_trackers is a tracker you own in the same space
  2. Update client parsers — remove handling for visibility, star_count, usage_count, is_public, and published_at
  3. Update cost estimates — linked trackers are free; use current reasoning-mode multipliers (basic ×1, advanced ×6, super ×18, zen ×40)
  4. Long-running runs — use async mode (sync: false) for zen and for any client with a short HTTP timeout

Bidirectional score threshold alerts​

Tracker email and webhook alerts can fire on a lower bound, an upper bound, or both at once — e.g. alert when score ≤ 20 or ≥ 80. Alert emails include a short trigger reason indicating which bound was crossed.

Console​

  • Below / Above checkboxes replace the single-direction radio buttons; both can be enabled together.
  • A dual-thumb slider appears when both directions are selected; a single slider is shown when only one direction is active.
  • Validation requires at least one direction when email or webhook is enabled, and lower ≤ upper when both bounds are on.

Notifications​

notification_config accepts:

  • notify_below + lower_threshold — notify when score <= lower_threshold
  • notify_above + upper_threshold — notify when score >= upper_threshold

API​

  • POST /v1/api/spaces/{space_id}/trackers and PATCH /v1/api/trackers/{tracker_id} accept the notify_below / lower_threshold / notify_above / upper_threshold fields on notification_config.
  • Invalid values return 422 validation errors.

Legacy score_threshold + threshold_direction remain supported for existing trackers. No action is required — trackers without the new fields keep their current behavior.