> For the complete documentation index, see [llms.txt](https://daddy-studios.gitbook.io/daddy-studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-admin/integrations.md).

# Integrations

Nothing below is required. Each resource is detected when it is running, and a feature whose resource is missing hides itself or shows a short note instead of failing.

| Area                 | Resources                                                                                                                                                                     |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Framework            | qbx\_core, qb-core, es\_extended (an ND\_Core bridge is included but not tested)                                                                                              |
| Inventory            | ox\_inventory, qb-inventory, ps-inventory, lj-inventory, jpr-inventory, qs-inventory, codem-inventory, core\_inventory, tgiann-inventory, origen\_inventory                   |
| Target               | ox\_target, qb-target, or a built-in ox\_lib fallback                                                                                                                         |
| Phone & social media | lb-phone, npwd, gksphone, qs-smartphone, qs-smartphone-pro with social accounts; qb-phone, high-phone, roadphone, okokPhone, yseries, d-phone with the framework phone number |
| Appearance           | illenium-appearance, fivem-appearance, qb-clothing, esx\_skin                                                                                                                 |
| Billing              | okokBilling, esx\_billing, phone invoices (qb-phone / jim-payments)                                                                                                           |
| Properties           | ps-housing, qb-houses, qs-housing, qb-apartments, esx\_property, loaf\_housing                                                                                                |
| Society accounts     | qb-management, qb-banking, Renewed-Banking, okokBanking, esx\_addonaccount                                                                                                    |
| Medical              | qbx\_medical, wasabi\_ambulance, qb-ambulancejob, esx\_ambulancejob, ml\_healthsystem                                                                                         |
| Fuel                 | ox\_fuel, LegacyFuel, cdn-fuel, ps-fuel, lj-fuel, qb-fuel, lc\_fuel, x-fuel, rcore\_fuel, ti\_fuel, okokGasStation, gacha\_fuel, hrs\_fuel, nd\_fuel                          |
| Weather              | qbx\_weathersync, Renewed-Weathersync, vSync and others                                                                                                                       |
| Screenshots          | screenshot-basic                                                                                                                                                              |

Server start was tested with Qbox + ox\_inventory, QBCore + qb-inventory and ESX + ox\_inventory. If a script you use is not picked up, open a ticket on our Discord with the resource name.

## Editing a bridge

Every integration lives in `bridge/` and stays editable in the escrow edition, together with `config/` and `locales/`. Each file starts with a plain definition table, so supporting a renamed resource or a custom database table usually means adding one entry.

| File                                                    | Contents                                                                 |
| ------------------------------------------------------- | ------------------------------------------------------------------------ |
| `bridge/framework/*.lua`                                | Player access, jobs, gangs and the item list per framework               |
| `bridge/inventory/*.lua`                                | Inventory adapters, including the item catalog                           |
| `bridge/server/phone.lua`                               | Phone numbers and social media accounts                                  |
| `bridge/server/billing.lua`                             | Unpaid bills                                                             |
| `bridge/server/housing.lua`                             | Owned properties                                                         |
| `bridge/server/societies.lua`                           | Job and gang accounts                                                    |
| `bridge/server/licenses.lua`                            | Licenses                                                                 |
| `bridge/server/appearance.lua`, `bridge/appearance.lua` | Ped persistence, outfits and the clothing menu                           |
| `bridge/server/catalog.lua`                             | Jobs, gangs, items and vehicle models in the panel pickers               |
| `bridge/server/garages.lua`                             | Garage list for the Give vehicle window, extra garages and plate formats |
| `bridge/fuel.lua`                                       | Fuel scripts                                                             |

Job, gang, item and vehicle pickers read their lists from the running framework and inventory, with the `jobs`, `job_grades`, `items` and `vehicles` tables as a fallback on ESX.


---

# 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://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-admin/integrations.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.