> 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/integration-readiness.md).

# Integration Readiness

| Capability                                   | Readiness                                             |
| -------------------------------------------- | ----------------------------------------------------- |
| Operator-seeded bounded sponsorship          | Available for controlled Preprod integration          |
| Signed execution receipts                    | Reference engineering proven; public verifier pending |
| Generalized self-service provider onboarding | Blocked on wallet signing                             |
| Public multi-application API                 | Not yet released                                      |
| Independent multi-operator routing           | Planned                                               |
| Production SLA and tariffs                   | Not defined                                           |

## Appropriate current use

The appropriate current integration is a capped Preprod pilot with explicit application identity, operation scope, capacity budget and evidence capture.

Ura does not claim unrestricted production sponsorship or generalized public liquidity.


---

# 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/integration-readiness.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.