> This page is for The Console.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://infonite.dev/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://infonite.dev/_mcp/server.

# Engines

An **engine** is one connector: one bank, one utility, one public administration, on one channel. The [*Engines*](https://www.infonite.tech/console/engines/) screen of the Console is the whole catalogue — everything that exists on the platform, not only what your application is authorized to run — so it is where you find out what is possible before you ask for it.

---

## Reading the catalogue

#### Start from the categories

The top of the screen counts the engines by category — banks, utilities, public administrations — and by market. Click a category to keep only its engines; click **Total** to see them all again.

#### Narrow it down

Search by name, filter by market, category or availability, and sort. Active filters show under the bar, with one click to clear them.

#### Pick the view you read best

The same catalogue as a **table**, with the details in columns, or as **cards**, with the logos. Your choice is remembered.

#### Open an engine

Each engine opens its own sheet: what it returns — the [features](/guides/features) and the [data models](/guides/data-models/overview) behind them — how it is connected, its availability and its notes.

---

## Availability, and asking for more

What an engine's sheet says about availability is about **the platform**: whether the engine is live, in what markets, on what channel. Whether **your application** may run it is a separate question, answered per application when it moves to production — see [organizations and applications](/console/organizations-and-applications#the-applications).

> **Tip**
>
> **Seeing an engine you cannot run yet is the point.** Everything in the catalogue exists. If your application needs one it is not authorized for, ask: `support@infonite.tech`, with the engine's name and what you want it for.

#### [Run one directly](/direct-executions/overview)

From your backend, with credentials you provide: a direct execution.

#### [Run one in a flow](/guides/what-is-a-flow)

Inside our widget, with the person there to log in: a flow.