> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/getting-started/what-can-i-build.md).
# What can I build?
Jet Admin builds apps around the data and work your team already has. You can start with a prompt, connect existing records, and then add screens, actions, permissions, workflows, or agents as the job requires.
## Internal tools
Give an operations or support team a workspace to search records, update statuses, and make decisions. An inventory console might show stock levels, let approved users change a quantity, and record the result.
## Customer portals
Let customers sign in to see their own orders, tickets, or account details. Start with the data they should see, then test [authentication and permissions](/access-and-sharing/start-here.md) with a customer account before sharing.
## Dashboards and approvals
Turn connected data into a dashboard for the measures people actually use. Add an [approval workflow](/workflow/practical-guides/create-an-approval-process.md) when a change needs review before it takes effect.
## AI agents
An [agent](/ai-agents/overview.md) can use instructions and tools to handle tasks that need context or several connected systems. Test its access and write actions before running it with real records.
Jet Admin supports [200+ integrations](https://www.jetadmin.io/integrations), including databases, APIs, and business apps. You can also use [Jet Databases](/user-guide/jet-databases.md). For a first build, pick one concrete task and follow [Build your first app with AI](/getting-started/start-here.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
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.jetadmin.io/getting-started/what-can-i-build.md?ask=&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.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
