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

# Developers

Build applications that submit and track AI Tasks on TrueOpen.

This section is for application developers who consume compute through TrueOpen. It follows the application journey rather than the implementation of Cortex or the chain.

An application integration will normally:

1. Create or load a user account.
2. Discover a suitable model Profile.
3. Create a session and fund a Task order.
4. Submit input data and a signed order.
5. Track Worker selection, inference, and verification.
6. Retrieve and validate the result.
7. Open a challenge when the accepted result does not satisfy the Profile rules.

## Public interfaces

The application guides will document:

* SDK installation and supported environments
* Account creation and signing
* Profile discovery
* Session and Task submission
* Result retrieval and status tracking
* Challenge submission
* Public chain and Nexus APIs
* Error handling, retries, and idempotency

Concrete API quickstarts will be published with the corresponding SDK packages, endpoints, network configuration, and compatibility guarantees. Start with [Application integration](/developers/application-integration.md) for the application responsibilities and [Task lifecycle](/protocol/v1/tasks.md) for the interaction sequence.

If you want to supply inference or verification capacity, start with [Providers](/providers.md). If you are implementing the service behind Cortex, use [Model integration](/providers/model-integration.md).


---

# 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.trueopen.ai/developers.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.