Skip to main content
Kylon proxy calls are checked and recorded against workspace credits where applicable.

​
Preflight checks

Before a proxy request is sent to a provider, Kylon may check:
  • Whether the workspace has enough credits
  • Whether the request is allowed by a script-level credit policy
  • Whether the available credit grants permit a restricted capability, when an endpoint requires one
A normal insufficient-credit check returns 402 payment_required. A credit grant that does not cover a restricted capability returns 402 with error: "credit_capability_required". Suspended or deleting workspaces are refused with 403. A matching agent skill is not a provider-route gate. Script calls can also hit a call burst limit or a script credit limit. Both return 429 with error: "script_credit_rate_limited". Where the call limiter counts a request, the response includes these headers, including on streamed responses and errors: Follow the returned guidance and Retry-After: script-policy refusals can require user approval before work resumes. Do not assume an immediate retry will resolve a credit or policy refusal.

​
Fixed-cost endpoints

Some endpoints have fixed credit costs. Examples include:

​
Dynamic-cost endpoints

Some providers are accounted from returned usage:

​
Zero-cost routes

Discovery and catalog endpoints do not all have the same billing behavior as execution endpoints. Kalodata currently records zero-credit usage. OpenRouter video status and content requests have no separate request charge, while a completed status response may cause generation-cost reconciliation.

​
Streaming requests

For streaming model requests, Kylon records usage after the stream completes or disconnects. If the client disconnects, the request is stopped and recorded as disconnected.

​
Error accounting

Failed provider requests are still recorded with status code, provider, endpoint, model when available, and a short error summary. This helps teams understand which calls are failing and why.