Capabilities
Choose the Right Capabilities
Start with the customer's desired outcome. Add only the capabilities required to complete that outcome, then test them before publishing.
Decision Guide
| Requirement | Recommend | Why |
|---|---|---|
| Answer FAQs from files or a website | Knowledge source | Retrieval is enough; no action is required |
| Book a confirmed time | Appointment Booking Kriya | The agent can create a calendar appointment |
| Recommend products, services, or menu items | Product Catalog Kriya | Structured catalog data supports search, pricing, and availability |
| Perform an action in another business system | Custom MCP Kriya | MCP exposes external tools to the agent |
| Add a public website chat | Public Chat or Hosted Chat | Designed for unauthenticated public entry points |
| Call the agent from a backend or internal system | Secure Chat API | Uses a workspace API key and keeps credentials server-side |
Ask Before You Configure
For appointment booking:
- Should bookings use Kriya Calendar or an existing Google Calendar?
- What timezone, business hours, slot length, and parallel-booking limit apply?
For a product catalog:
- Are these products, services, or both?
- Which prices, currencies, availability states, and purchase links should customers see?
For Custom MCP:
- What MCP server URL and authentication mode are required?
- Should the agent access every discovered tool or only selected tools?
For an API integration:
- Is the caller a browser or a trusted server?
- Should the conversation continue by sending the returned session ID?
- Does the UI need streaming and tool-activity events?
Least Privilege
Enable only the Kriyas and MCP tools an agent needs. A capability binding is permission for the agent to use that action during a conversation.