STEP 05 OF 07

Kylon Proxy

Kylon Proxy and Connections

Use Kylon Proxy for Kylon-provided services. Use a Connection for an account or API key you bring.

Kylon Proxy
Routes authenticated Agent requests to supported model, search, scraping and media services using Kylon’s upstream accounts. Usage draws on workspace credits.
Connection
Uses your external account or key, subject to its access grants and the provider’s charges. Some tool usage can also incur Kylon charges.
Request flow
Agent → authenticated request → permitted service → result. Kylon records Proxy usage and checks credits.
Example
Research a client’s market with supported search or scraping services through Proxy; read the client’s own mailbox through an authorized Connection.

Bringing a service API key through a Connection does not mean every built-in Agent model supports a bring-your-own-key option.

Try it

Use case and hands-on

Try both routes with test data, then compare the account and access each one uses.

  1. 01

    Ask a Kylon Agent to summarize a market question using named public sources. Its model runs through Kylon Proxy and uses workspace credits.

  2. 02

    Connect a test inbox you own, grant one Agent access, and ask it to summarize five messages. The Connection uses that account under its provider's terms.

  3. 03

    Have a teammate without inbox access ask a second Agent with no grant to read it. Check that the request is denied.

Use test accounts. When you trigger a task yourself, an Agent may borrow your Connection access; that is not a valid denial test.