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 agent has access to the requested provider capability
If a credit check fails, the proxy returns 402 payment_required.

​
Fixed-cost endpoints

Some endpoints have fixed credit costs. Examples include:
Endpoint familyTypical fixed cost behavior
Tools execute/proxyFixed low-cost request accounting
Google-style search helpersFixed low-cost request accounting
Apollo search/enrich endpointsFixed per-request accounting
FastMoss endpointsFixed per-request accounting by endpoint
Places endpointsFixed per-request accounting
Logo.dev endpointsFixed per-request accounting
ScrapeCreators endpointsProvider response may include its own credit estimate, with a default fallback

​
Dynamic-cost endpoints

Some providers are accounted from returned usage:
Provider familyUsage signal
OpenAI-compatible model routesToken and image usage
Anthropic-compatible model routesToken usage
Gemini-compatible model routesToken and media usage metadata
Cerebras-compatible model routesToken usage
OpenRouter model routesToken usage
ElevenLabs-compatible routesCharacter usage
Apify actor runsActor compute units
Seedance video generationEstimated video compute units

​
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.