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

# Frends Development

- [Centralized Portal](https://docs.frends.com/docs/frends-6.1.0/frends-development/centralized-portal.md): From featured content on the Start page, to Process Editor and managing your Agents, Frends Control Panel has it all.
- [Frends Portal](https://docs.frends.com/docs/frends-6.1.0/frends-development/centralized-portal/frends-portal.md): Management for your Frends Tenants.
- [Control Panel](https://docs.frends.com/docs/frends-6.1.0/frends-development/centralized-portal/control-panel.md): All the integration magic happens within Frends Control Panel.
- [Integrations](https://docs.frends.com/docs/frends-6.1.0/frends-development/integrations.md): Frends is an integration platform, after all.
- [Low-code Development](https://docs.frends.com/docs/frends-6.1.0/frends-development/integrations/low-code-development.md): We have visual process editor, enhanced with C# code.
- [Connectors](https://docs.frends.com/docs/frends-6.1.0/frends-development/integrations/connectors.md): Tasks and triggers are the key building blocks of integrations in Frends.
- [Reusable Content](https://docs.frends.com/docs/frends-6.1.0/frends-development/integrations/reusable-content.md): Keeping yourself DRY makes things more simple.
- [Templates](https://docs.frends.com/docs/frends-6.1.0/frends-development/integrations/templates.md): Starting point for your own customizations.
- [API Management](https://docs.frends.com/docs/frends-6.1.0/frends-development/api-management.md): Creating and managing APIs has never been easier.
- [API Specification](https://docs.frends.com/docs/frends-6.1.0/frends-development/api-management/api-specification.md): Creating an API is as easy as defining the OpenAPI specification.
- [Passthrough APIs](https://docs.frends.com/docs/frends-6.1.0/frends-development/api-management/passthrough-apis.md): Coherent API endpoints without extra fluff.
- [API Policies](https://docs.frends.com/docs/frends-6.1.0/frends-development/api-management/api-policies.md): Authentication and logging rules for your API endpoints.
- [API Monitoring](https://docs.frends.com/docs/frends-6.1.0/frends-development/api-management/api-monitoring.md): Monitor all the connections to your Tenant.
- [API Portal](https://docs.frends.com/docs/frends-6.1.0/frends-development/api-management/api-portal.md): Effortlessly create and publish your API docs.
- [AI features](https://docs.frends.com/docs/frends-6.1.0/frends-development/ai-features.md): In Frends, AI is not an afterthought.
- [AI Assisted Development](https://docs.frends.com/docs/frends-6.1.0/frends-development/ai-features/ai-assisted-development.md): AI in Frends will help you with configuring Tasks as well as create code.
- [Documentation Generation](https://docs.frends.com/docs/frends-6.1.0/frends-development/ai-features/documentation-generation.md): Automate the least favorite task of all development with AI.
- [Intelligent AI Connector](https://docs.frends.com/docs/frends-6.1.0/frends-development/ai-features/intelligent-ai-connector.md): Allowing AI to participate in your Processes.
- [Frends Platform API](https://docs.frends.com/docs/frends-6.1.0/frends-development/frends-platform-api.md): Manage and operate your Frends Tenant using 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://docs.frends.com/docs/frends-6.1.0/frends-development.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.