Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.kyberis.ai/llms.txt

Use this file to discover all available pages before exploring further.

Kyberis errors are structured for agent branching.

​
Error fields

FieldMeaning
error_codeStable machine-readable error code
messageHuman-readable summary
status_codeHTTP status code
request_idRequest correlation ID
run_idAgent run ID when context is available
step_idAgent step ID when context is available
required_scopesScopes needed to call the endpoint
reasonAdditional machine-readable blocker
retry_after_secondsBackoff hint for rate limits
requested_credits / available_creditsCredit exhaustion details

​
Common statuses

StatusTypical causeAgent action
400Missing or malformed agent_context, subject/query conflict, bad request shapeFix the payload.
401Missing, invalid, or expired credentialsRefresh credentials or ask for a valid key.
403Missing scopeAsk for a key with required_scopes.
422Schema validation failureCorrect fields, enums, limits, or types.
429Rate limit or repeated auth failuresBack off and honor retry_after_seconds.
5xxTransient service failureRetry conservatively with backoff.

​
Do not retry blindly

Do not retry these without changing something:
  • insufficient_scope
  • credit_exhausted
  • batch_limit_exceeded
  • validation errors
  • malformed or expired connect tokens

​
Error report shape

When a Kyberis call fails, report: 
Kyberis call failed: <endpoint>
status: <status_code>
error_code: <error_code>
request_id: <request_id>
run_id: <run_id>
step_id: <step_id>
required action: <credential, scope, payload, retry, or support action>