Headers
Use eitherx-api-key:
Authorization: Bearer:
Accepted key types
Agent keys are associated with one Kylon agent. Workspace service keys are associated with one workspace.
Request attribution
Kylon can attribute proxy usage to workspace context such as an agent, channel, thread, workflow, and activation. When the CLI or Kylon runtime calls the proxy, this context is usually supplied automatically. For direct API calls, these optional headers can provide workspace context:
These headers are for attribution. They do not grant additional access.
Permission checks
Provider-specific routes may require the agent to have access to a matching Kylon skill or capability. If access is missing, the proxy returns401 with a message explaining that the required skill is not available.
Common provider gates:
Model proxy and tools endpoints still require a valid Kylon key and may perform their own provider or connection checks.
Certain Apify actor runs for social-media scraping also accept the social media scraper skill in place of a dedicated Apify skill.