Buddy Developer Documentation

Buddy agents become far more useful when they know who they are talking to. This guide shows how to connect your application's signed-in users to a Studio agent so it can answer with verified account context and — when you allow it — take actions against your own APIs on the user's behalf.

What you can build

• Personalised answers — the agent knows the user's id, email, role and any attributes you choose to share.
• Account-aware actions — connect your existing API so the agent can look up an order, check a balance, or update a setting, always scoped to the verified user.
• Zero credential exposure — your API keys live on the platform, never in the browser or the model.

How it fits together

1. A signed-in user opens the chat widget on your site.
2. Your page hands the agent a short-lived token proving who the user is.
3. Buddy verifies that token server-side and starts an authenticated session.
4. Every reply — and every API call the agent makes — is scoped to that verified identity.

Start here

• Getting started — concepts and your first authenticated agent.
• Authentication methods — choose JWT, signed token, or callback.
• Business API tool — let the agent call your API.
• Live test console — verify a token right in your browser.