# Query Agent

The **Weaviate Cloud (WCD) Query Agent** provides an interactive console for using the Weaviate [Query Agent](../agents/overview.md), a pre-built agentic service designed to answer natural language queries based on the data stored in Weaviate Cloud.

The user simply provides a prompt/question in natural language, and the Query Agent takes care of all intervening steps to provide an answer.

## Query a collection

In order to use the Query Agent, log into your Weaviate Cloud account and select `Agents` in the sidebar panel.

[Embedded content embed](https://app.guideflow.com/embed/zkjyx88tek)

## Additional parameters for querying

In addition to selecting one or more collections to query, you can also:

- Specify API keys for external model providers (like OpenAI, Anthropic, etc.)
- Select which vectors in a collection to query (if there are multiple vectors in the collection)
- Specify a _system prompt_ that provides additional information or instructions to the agent (for example, setting the tone, language, etc.)

[Embedded content embed](https://app.guideflow.com/embed/mk68j60hqp)

## Generate code snippets

After executing a query, you can also generate a code snippet that performs the same task through one of the available Query Agent client libraries, either Python or TypeScript.

[Embedded content embed](https://app.guideflow.com/embed/zklz3v9sop)

## Usage and limitations

### Usage limits

Each Weaviate Cloud [organization](../cloud-account-management/users-and-organizations.md#organizations) can make up to 1,000 Query Agent requests per month at no cost.

Requests are consumed based on query type:

- `Ask`: 4 requests per query
- `Search`: 1 request per query
- `Suggest Queries`: 1 request per query

This limit may change in the future. For questions about usage limits, contact product@weaviate.io.

![Weaviate Cloud Console Query Agent Usage](/assets/docs/cloud/img/weaviate-cloud-qa-usage.png)

You can track your organization's Query Agent usage directly in the Console.

### Custom collection descriptions

The Query Agent makes use of each collection's `description` metadata as well as individual property descriptions in deciding what collection to query.

Both collection descriptions and property descriptions can be updated after the collection has been created. For detailed instructions on updating collection and property descriptions, see the [update collection definition documentation](../how-to-manage-collections/collection-operations.md#update-a-collection-definition).

We are investigating an ability to specify a custom collection description at runtime.

### Execution times

The Query Agent performs multiple operations to translate a natural language query into Weaviate queries, and to process the response.

This typically requires multiple calls to generative models (e.g. LLMs) and multiple queries to Weaviate.

As a result, each Query Agent run may take some time to complete. Depending on the query complexity, it may not be uncommon to see execution times of \~10 seconds.

**For long-running or complex queries**, consider using [streaming responses](../modes/ask-mode.md#streaming) rather than non-streaming requests. Streaming provides progress updates and sends heartbeats to maintain the connection, preventing timeout issues that can occur with long-running non-streaming requests.

### Multi-tenancy

The WCD Query Agent does not support multi-tenancy. In order to utilize multi-tenancy with the Query Agent, use a [client library](../agents-configuration/advanced-collections.md).

## Further resources

- [Query Agent](../agents/overview.md)

## Support

If you use **Weaviate Cloud** (Database cluster(s) or Weaviate product in the cloud) or have a self-hosted support package, open a ticket in the [Support Portal](https://support.weaviate.io) or email [Weaviate support](mailto\:support@weaviate.io) directly. To add a [support plan](https://weaviate.io/support-plans), contact [Weaviate sales](https://weaviate.io/pricing#contact-sales).

Use the **Support Portal** for direct help from the Weaviate team: open and track tickets, and we'll respond in line with your support plan. The **Community Forum** is open to everyone, and a great place to ask questions, get help with your cluster, and connect with other developers. For all the ways to get help, see the [Support overview](../support/overview.md).

::::card-grid
:::card{title="Weaviate Support Portal" href="https://support.weaviate.io" icon="headset"}
Direct help from the Weaviate team for Weaviate Cloud. Open and track tickets in the **Support Portal**.
:::

:::card{title="Weaviate Community Forum" href="https://forum.weaviate.io/c/support" icon="messages-square"}
Ask questions, share ideas, and connect with other developers on our **Community forum**.
:::
::::

## Related pages

- [Agents](./agents-index.md)
- [AI-assisted Weaviate code generation](./ai-assisted-vibe-coding-index.md)
- [APIs](./apis-index.md)
- [Authorization and authentication](./authorization-and-authentication-index.md)
- [Benchmarks](./benchmarks-index.md)
- [Best practices](./best-practices-index.md)
- [Client libraries](./clients-index.md)
- [Client Libraries / SDKs](./client-libraries-index.md)
- [Cloud](./cloud-index.md)
- [Cloud account management](./cloud-account-management-index.md)

# Agent Instructions

This portal answers questions programmatically. To receive a synthesized,
source-cited answer instead of crawling page by page, append the `?ask=`
query parameter to any page URL on this site:

    /guides/quickstart?ask=how+do+I+authenticate

Optional parameters:

- `&goal=<what-you-are-trying-to-do>` steers the answer toward your
  objective (e.g. `&goal=write+a+python+client`).
- `&version=<label>` scopes the answer to a mounted version when the
  portal publishes more than one.

The response is `text/markdown`: the answer followed by a `# Sources` list
of the portal pages it was grounded in. Status codes are the contract:

- `200` — the answer; `402` — the portal owner’s plan or answer credits are
  exhausted (surface this to your operator; do NOT retry); `429` — you are
  rate-limited; back off for the `Retry-After` seconds; `503` — the answer
  lane is temporarily unavailable; fall back to crawling the `.md` pages.

For the full corpus map read `llms.txt` at the site root; for the tool
surface (search + page fetch as MCP tools) see `/mcp`.
