Runtime model

Preview resources and lifecycle for launching agentic trading strategies through Naven.

The Strategy Runtime is Naven's primary agentic trading resource. It turns a reusable Strategy version into an independently funded, scheduled, and operated Agent.

This page describes the private-preview contract. Enabled Naven Projects can use these endpoints before general availability.

Strategy definition

A Strategy separates reusable logic from per-Agent operating settings.

{
  "name": "BTC Momentum",
  "visibility": "private",
  "version": {
    "kind": "quant_signal",
    "schemaVersion": 1,
    "definition": {
      "instructions": "Trade only when momentum confirms across the selected inputs.",
      "universe": ["BTC"],
      "dataSources": ["candles", "macd", "funding"],
      "candleInterval": "15m"
    }
  }
}

Publishing a new version does not mutate existing Runtimes. A Runtime stays linked to the exact version it was launched with until the product explicitly creates or performs an upgrade flow.

Runtime definition

{
  "strategyVersionId": "stgv_01k4...",
  "accountId": "acct_7nk2...",
  "name": "BTC Momentum Agent",
  "cronExpression": "*/15 * * * *",
  "fundLimitUsd": 1000,
  "maxLeverage": 2,
  "maxDrawdownPercent": 8,
  "idempotencyKey": "launch_user-42_btc-momentum"
}

Each Runtime has independent capital and risk settings. The same Strategy can therefore power a conservative Agent and an aggressive Agent without duplicating strategy logic.

Runtime lifecycle

provisioning → active ⇄ paused → stopped
       │          │         │
       └──────────┴─────────┴──→ failed / needs_review

State	Meaning
`provisioning`	Naven is creating or synchronizing the provider runtime
`active`	Scheduled and manual Executions are permitted
`paused`	No new scheduled Executions; the Runtime may be resumed
`stopped`	Terminal state; create a new Runtime to operate again
`needs_review`	Provider or Account state requires user attention
`failed`	Runtime provisioning or synchronization failed

Runtime controls are intentionally small: create, get, list, run now, pause, resume, and stop.

Execution record

An Execution is one evaluation of a Runtime, triggered by its schedule or a manual request.

{
  "id": "exec_01k4...",
  "runtimeId": "runtime_01k4...",
  "triggerType": "schedule",
  "scheduledAt": "2026-08-28T09:45:00Z",
  "status": "completed",
  "attemptCount": 1,
  "decision": {
    "action": "LONG",
    "instrument": "BTC"
  },
  "riskAssessment": {
    "approved": true,
    "accountEquityUsd": 1250
  },
  "order": {
    "side": "buy",
    "size": "0.003",
    "status": "filled"
  },
  "error": null
}

Decision and risk payloads remain flexible because providers may use different strategy engines. Stable fields cover ownership, time, trigger, lifecycle, attempt count, normalized order summary, and errors.

API surface

The first Naven contract stays narrow:

GET    /agentic-trading/strategies
POST   /agentic-trading/strategies
GET    /agentic-trading/strategies/:strategyId
POST   /agentic-trading/strategies/:strategyId/versions

GET    /agentic-trading/accounts
POST   /agentic-trading/accounts/agent-wallets

GET    /agentic-trading/runtimes
POST   /agentic-trading/runtimes
GET    /agentic-trading/runtimes/:runtimeId
PATCH  /agentic-trading/runtimes/:runtimeId/status

GET    /agentic-trading/runtimes/:runtimeId/executions
POST   /agentic-trading/runtimes/:runtimeId/executions

This surface is enough for another product to offer Strategy discovery, Agent launch, lifecycle controls, and execution history. Raw order placement, venue credentials, and provider-specific endpoints remain outside the public runtime contract.

Metering options

Naven can apply x402 or project billing at one or more boundaries:

Paid Strategy access.
One-time Runtime activation.
Per scheduled or manual Execution.
Paid market-data and research capability calls made by the Agent.

Metering is orthogonal to strategy implementation. A free internal Strategy and a paid public Strategy use the same Runtime contract.