# Ask Clio

## Ask Clio

- [Meet Ask Clio](https://ask-clio.gitbook.io/ask-clio/readme.md)
- [Quickstart](https://ask-clio.gitbook.io/ask-clio/getting-started/quickstart.md)
- [Setting up a sandbox environment](https://ask-clio.gitbook.io/ask-clio/basics/setting-up-a-sandbox-environment.md): Start here.
- [Web SDK Integration Guide](https://ask-clio.gitbook.io/ask-clio/basics/markdown.md): Web SDK Integration Guide
- [React Native SDK Integration](https://ask-clio.gitbook.io/ask-clio/basics/editor.md): Mobile SDK Integration Guide
- [White Labeling Ask Clio](https://ask-clio.gitbook.io/ask-clio/basics/white-labeling-ask-clio.md): Customizing the Ask Clio SDK
- [Human Help Desk](https://ask-clio.gitbook.io/ask-clio/basics/human-help-desk.md): Clients can contact your team for human support.
- [Compliance for Regulated Firms](https://ask-clio.gitbook.io/ask-clio/basics/compliance-for-regulated-firms.md)
- [Usage Limits](https://ask-clio.gitbook.io/ask-clio/basics/usage-limits.md)
- [Adding Dynamic Inputs: Secure, Firm-Defined Fields for Ask Clio API Calls](https://ask-clio.gitbook.io/ask-clio/tools-and-data-plug-in-your-apis/adding-dynamic-inputs-secure-firm-defined-fields-for-ask-clio-api-calls.md): Dynamic Inputs allow your firm to define arbitrary, secure fields that can be injected into Ask Clio tool calls at runtime.
- [Adding your Clearing Partner](https://ask-clio.gitbook.io/ask-clio/tools-and-data-plug-in-your-apis/adding-your-clearing-partner.md): How to integrate Ask Clio to your clearing partner
- [Integrations: Add your own APIs](https://ask-clio.gitbook.io/ask-clio/tools-and-data-plug-in-your-apis/integrations-add-your-own-apis.md): Add you own firm APIs for your bot to access
- [Adding Authentication Profiles to Access Your APIs](https://ask-clio.gitbook.io/ask-clio/tools-and-data-plug-in-your-apis/adding-authentication-profiles-to-access-your-apis.md): This is how you can add your authentication profiles to access you APIs.
- [Secure Client Confirmation & Confirmed Action](https://ask-clio.gitbook.io/ask-clio/tools-and-data-plug-in-your-apis/secure-client-confirmation-and-confirmed-action.md)
- [MCP <> Connecting Your Clients' AI Assistants](https://ask-clio.gitbook.io/ask-clio/mcp-less-than-greater-than-connecting-your-clients-ai-assistants.md)
- [Ask ClioWorkflows + Context —Website Integration Guide](https://ask-clio.gitbook.io/ask-clio/adding-context-and-custom-workflows/ask-clioworkflows-+-context-website-integration-guide.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
This site has an agentic ask interface you may use to query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ask-clio.gitbook.io/ask-clio/index.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.