> For the complete documentation index, see [llms.txt](https://dev.flexshopper.com/medusa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.flexshopper.com/medusa/readme.md).
# Introduction
Welcome to the FlexShopper API. We're excited to partner with you!
There are two ways to integrate with FlexShopper:
Medusa
A powerful REST API that you can call from anywhere.
## Medusa
[Medusa](/medusa/integration-guides/medusa.md), our REST API, is suitable for you either if you don't have a **web** application, or if you're simply seeking more control over your visual interface. Medusa enables you to integrate with FlexShopper while preserving your own application's look and feel.
{% hint style="success" %}
We strongly recommend using the Medusa integration.
{% endhint %}
{% content-ref url="/pages/RC54UowFsRbkvi1Yw4Wa" %}
[Medusa](/medusa/integration-guides/medusa.md)
{% endcontent-ref %}
## Payment Plugin
[Payment Plugin](/medusa/integration-guides/payment-plugin.md), the suite of web components and iframe, is suitable for you if you already have a customer-facing **web** application UI. This integration is typically the easiest of the two, but requires you to already have a web application to embed Payment Plugin into as an iframe.
{% content-ref url="/pages/5aLfZp5RsTcdpOxBbsY0" %}
[Payment Plugin](/medusa/integration-guides/payment-plugin.md)
{% endcontent-ref %}
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://dev.flexshopper.com/medusa/readme.md?ask=&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 `build a script that syncs our docs to a CMS` 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.
