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

# Service (API) Editor

{% hint style="info" %}
Coming soon in v3.1.1
{% endhint %}

The **Service (API) Editor** allows users to create and manage the backend services that power their applications. Through natural language, users can describe or modify how data should be processed, retrieved, or connected between different parts of the app. The system interprets these inputs and automatically generates the corresponding service code.

Every description and code snippet remain synchronized, ensuring that what users define conceptually always matches the actual backend implementation. This feature helps maintain clarity and consistency across the system, making it easier to update logic, link data models, or adjust workflows as the application evolves. It bridges the gap between idea and execution, allowing users to design functional APIs without needing to write code manually.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.quantumbyte.ai/components/studio/service-api-editor.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.