> For the complete documentation index, see [llms.txt](https://docs.contextual.io/documentation-and-resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.contextual.io/documentation-and-resources/patterns/solution-architecture.md).

# Solution Architecture

The critical components of any Contextual solution architecture will consist of:

* Data - Contextual manages data via JSON Schema definitions within our Object Types Component. We provide a basic template schema in the definition that you can edit manually or using our AI Assistant.
* APIs (accessing Contextual Object Types) - As soon as you define a data Object Type in Contextual we instantly create an API that you can create a key for in order to provide access to those objects with pre-build create, edit, search and more functions.
* Business Logic - Contextual provides a low-code visual editor called Flows based on Node-RED. Drag and drop nodes that create or update data records, execute javascript functions, run machine learning models and more.
* APIs (accessing Contextual Flows) - Use HTTP Flows to create Get and Post endpoints that can serve as API endpoints into Contextual to drive Flows or serve web content.
* Connections (access services / APIs outside of Contextual) - Connections capture credentials to third party data sources or AI tools or systems.
* Agents - Agents allow for you to allocate compute to Flows such that they operate in production and are 'deployed'.

With the combination of data, business logic, connections and compute you can build solutions of any complexity.


---

# 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.contextual.io/documentation-and-resources/patterns/solution-architecture.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.