> For the complete documentation index, see [llms.txt](https://ura-labs-1.gitbook.io/ura-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ura-labs-1.gitbook.io/ura-documentation/developer-integration.md).

# Developer Integration

Current integration model, sponsorship lifecycle and readiness boundaries.

Ura's developer path is designed for applications that need bounded Midnight execution without requiring every end user to acquire and manage DUST first.

## Sponsored execution lifecycle

1. The application creates an identifiable, bounded sponsorship request.
2. Policy checks validate the application, operation, budget and current capacity.
3. Capacity is reserved for the accepted request.
4. The warm operator submits the Midnight execution.
5. Confirmation is observed and classified.
6. Ura returns a receipt and records the spend in append-only reconciliation.

## Current integration boundary

* Bounded operator-seeded sponsorship is proven.
* Partner integration exists as reference engineering, not as an unrestricted production API.
* Canonical request identity, replay and expiry hardening remain active work.
* Multi-operator routing, failover and production service levels are not yet claimed.

## What integrators should expect

A production integration must make the application identity, requested operation, budget, expiry and terminal result explicit. Retryable failures must remain distinguishable from rejected or completed operations.

Technical integration access is currently coordinated directly with Ura Labs while the public interface is hardened.


---

# 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://ura-labs-1.gitbook.io/ura-documentation/developer-integration.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.