Concepts

Turaxia is small enough to describe in six objects and three rules.

Objects

• Workspace — the top-level scope. Every API key, webhook, audit event, and primitive call belongs to exactly one workspace.
• Service account — a machine identity inside a workspace. Connect provisions service accounts; they hold API keys.
• API key — a workspace-scoped secret used to call REST, SDK, CLI, or MCP. Scoping is per-module.
• Product record — the typed object every primitive consumes and emits. Fields include productId, title, variants, images, materials, pricing, and per-field confidenceSignals.
• Audit event — a typed event emitted by every primitive (parse.executed, localize.executed, price.quote.generated, route.resolve.generated, route.package_plan.generated).
• Scenario — a reproducible benchmark scope identified by a string id. Every card in the proof bundle references exactly one scenario.

Rules

• Typed in, typed out. Every primitive has a declared input and output schema. Agents can call them with or without a human in the loop.
• Confidence over guessing. Primitives never hallucinate. When a field cannot be derived with confidence, the output is null and a confidence signal is emitted.
• Reproducible or unpublished. A benchmark exists if and only if it produces a card in the public proof bundle.

Flow of data

supplier URL / raw HTML
  └─ Parse        → product record + confidence signals
       └─ Localize → translated record
             └─ Price.quote → landed cost in target currency
                   └─ Route.resolve → carrier + package plan

Module availability

Every module is labelled generally available, in beta, or in private alpha. The current state for every module lives on the developer hub.