> For the complete documentation index, see [llms.txt](https://genos-docs.gitbook.io/default/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://genos-docs.gitbook.io/default/v1.9.3/advanced-tutorials/guides/api.md).

# API 활용

**API 활용**

* **워크플로우 API 사용**: 생성한 워크플로우를 API로 호출하여 자동화된 처리를 수행하는 방법입니다.
* **채팅 API 사용**: 채팅 기능을 시스템과 연동하여 API 기반으로 활용하는 방법입니다.
* **LLM 서빙 API 사용**: 서빙된 LLM 모델을 애플리케이션에서 API로 호출해 사용하는 방법입니다.
* **멀티모달 서빙 API 사용**: 멀티모달 서빙을 API로 호출해 다양한 입력을 처리하는 방법입니다.


---

# 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://genos-docs.gitbook.io/default/v1.9.3/advanced-tutorials/guides/api.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.

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.