Choose a developer integration path
Open **Developer** from the sidebar. **Integration paths** helps you choose the direction of data exchange. Public example guides are available there; revealing this workspace’s exact MCP server URL additionally requires Connected AI view permission and enabled workspace access.
Build with MCP
Use **Open Connected AI** to set up an authorized app. When available, copy **MCP server URL**, choose **Connect an AI client**, or **Copy a build prompt**. OAuth and scoped permissions control access. Start by inspecting the workspace and requesting only the needed read access before enabling actions.
Simple URL: Fusion to your server
Choose **Simple URL → View Simple URL example** when Fusion should send an order to your HTTPS endpoint and receive a final customer-safe result in the same response. The page’s **Build prompt** asks the AI to inspect your project and implement field validation safely. Copying it does not send an order. Example: https://github.com/dhru-com/fusion-pro-simple-url
Reseller API: your app to Fusion
Choose **Reseller API → View Reseller API examples** for a server-side application that reads the catalogue/account, places orders, and tracks results. Begin with read-only methods. A real order can debit the reseller wallet; the page explicitly warns that there is no dry-run. Keep its token on the server and require deliberate approval before a paid test. Examples: https://github.com/dhru-com/reseller-api
Custom Payment Gateway
Choose **Custom Payment Gateway → View payment gateway development kit** for hosted middleware between Fusion and a real provider. **Provider implementation required** means the kit does not automatically supply a working provider connection. Verify payment server-side; a browser return is not proof that payment succeeded. Kit: https://github.com/dhru-com/payment-gateway-development-kit
Use a build prompt safely
Copy the prompt for the selected integration into your development client. Review the proposed implementation before enabling credentials or paid actions. Keep tokens and provider secrets server-side, and verify the result before retrying or reporting success. The Developer page itself does not execute the copied prompt or mark an invoice paid.