> For the complete documentation index, see [llms.txt](https://support.airspacelink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.airspacelink.com/user-guides/airhub-r-api-licensing.md).

# AirHub® API Licensing

The AirHub<sup>®</sup> API delivers essential data and services designed to power and enrich your Unmanned Aircraft System (UAS) applications. Built on a RESTful architecture, the API features predictable, resource-oriented URLs, handles both form-encoded and JSON request bodies, and returns JSON-encoded responses. It adheres to standard HTTP response codes, authentication, and verbs for seamless integration.

Developers can explore and build with the AirHub<sup>®</sup> API in a dedicated sandbox environment, ensuring that development and testing do not impact live data or production systems.

**Access the AirHub**<sup>®</sup> **API Developer Site:** For comprehensive documentation, API references, and to get started with integration, visit [airspacelink.com/developers](https://airspacelink.com/developers).


---

# 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://support.airspacelink.com/user-guides/airhub-r-api-licensing.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.