> For the complete documentation index, see [llms.txt](https://docs.codewords.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codewords.ai/readme.md).

# Welcome

Learn about CodeWords and how to get started

{% embed url="<https://www.youtube.com/watch?v=rzZxj6ptJ7M>" %}

CodeWords is an AI-powered platform that helps teams and individuals build AI agents, workflow automations, and full websites/apps. Unlike traditional automation tools, CodeWords lets anyone create powerful systems using natural language.&#x20;

Simply describe what you want to build or automate, and CodeWords turns your prompts into intelligent agents, workflows, websites, and apps that can plan, execute, and deliver results autonomously.

### What makes CodeWords Different?

Traditional automation tools require you to manually build, manage, and maintain every step of a workflow. CodeWords lets you build software through conversation. Just describe what you need, and Cody, your AI assistant, plans, builds, and delivers production-ready automations and apps inside a secure sandbox with internet access, automatic software installation, and 3000+ integrations.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.codewords.ai/readme.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 `build a script that syncs our docs to a CMS` 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.
