Pricing

Context Layer charges per execution of the runtime contract. You bring your own model provider keys (BYOK). Context Layer governs the execution boundary.

What counts as an execution?

• 1 invokeCL() runtime call equals 1 CL Execution.
• Flow workflows may include multiple executions depending on the number of steps.
• Conversational interactions in Pulse mode count one execution per request.
• Deterministic Flow replays return the previous result and do not consume executions.

If the execution limit is reached during a workflow, Context Layer allows the workflow to finish before rejecting new ones.

Every plan runs the same Context Layer runtime

Flow runtime
Pulse runtime
deterministic execution enforcement
canonical context assembly
authority contract enforcement
execution trace metadata
authority reports
BYOK provider access

Free: Builder Sandbox

1000 executions / month

≈ 200 workflow runs

No overflow.

Authority Reports
Execution Receipts
Metrics
Request Debugger

Get Started

Production: Core Runtime

$50 / month

10,000 executions / month

≈ 2,000 workflow runs

Overflow: $0.006 / execution

Authority Reports
Execution Receipts
Basic Metrics
Request Debugger

Start Production

Scale: High Throughput Runtime

$300 / month

100,000 executions / month

≈ 20,000 workflow runs

Overflow: $0.004 / execution

Authority Reports
Execution Receipts
Full Metrics
Request Debugger

Start Scaling

Deterministic replay prevents wasted executions

Flow executions are session-bound. If the same Flow step is repeated within a session, Context Layer returns the previous result instead of executing the runtime again.

Deterministic Flow replays therefore do not consume additional CL executions.

You are billed only when the runtime actually performs a new execution step.

What a typical workflow costs

A typical workflow may include multiple execution steps.

Example:

• classification
• planning
• generation
• verification
• final response

≈ 5 CL Executions

Example cost once included executions are exceeded.

Core Runtime overflow pricing
5 × $0.006 = $0.03 per workflow

High Throughput Runtime overflow pricing
5 × $0.004 = $0.02 per workflow

FAQ

A Context Layer execution is a single governed runtime operation performed under the Authority Contract.

No. Context Layer charges for runtime execution only. Model costs (tokens, API calls) remain with your provider through BYOK. You pay your provider directly for model usage.

Free plan: execution stops at 1000 per month. Production and Scale: overflow is billed at the per-execution rate ($0.006 and $0.004 respectively). No hard cutoff; execution continues.

Yes. Plan changes take effect at the next billing cycle. Upgrades apply immediately for the prorated difference. Downgrades apply at period end.

Yes. Each execution, whether Flow or Pulse, counts as one execution for billing. The execution mode does not affect the per-execution charge.