> For the complete documentation index, see [llms.txt](https://docs.fastn.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fastn.ai/build/unified-apis/unified-vs-direct.md).

# Unified vs direct

When to reach for a unified API and when to call the connector directly.

| Use a unified API when                                    | Use the connector directly when                      |
| --------------------------------------------------------- | ---------------------------------------------------- |
| Several providers do the same job for different customers | You need a field or action only one provider has     |
| You want one code path regardless of the customer's stack | The operation has no meaningful equivalent elsewhere |
| The fields you need are common across providers           | You are already deep in one vendor's model           |

The two are not exclusive: a workflow can use a unified endpoint for the common path and a direct connector action for the vendor-specific part.

### The All providers filter

Above the endpoint list, **All providers** shows the canonical surface; picking a single provider shows how that one behaves. Useful when a provider has a quirk you need to design around.


---

# 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://docs.fastn.ai/build/unified-apis/unified-vs-direct.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.