> For the complete documentation index, see [llms.txt](https://akiba-digital.gitbook.io/akiba-api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://akiba-digital.gitbook.io/akiba-api-docs/products/product-guideline.md).

# Product Guideline

## Modular Services

Our suite of API Products are consumable in various integration options to cater for your specialised needs

### Developer integration

This is our suite of endpoints, in one API. Strictly for the developers to plug into your application to call various endpoints, using our developer portal. Low cost solution for businesses with an existing platform.

Best suited for:

* Developed apps needing endpoints&#x20;
* A team with a developer to understand and integrate API

***

### Platform low-code integration

Our platform comes embedded with our APIs. For businesses that need an application origination system, powered by our APIs

Best suited:

* Business needing an application origination system&#x20;
* Little to no coding skills to implement

***

Next up, let's take a closer look on each:


---

# 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://akiba-digital.gitbook.io/akiba-api-docs/products/product-guideline.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.
