# Instant connectors

> Connectors that run on FlyMyAI's own key with no key from you - how an assistant or an agent finds, calls and prices them.

An **Instant** connector runs on FlyMyAI's own key for every account. There is
nothing to connect: no sign-in and no API key of yours. Your assistant finds it,
calls it, and each call is billed to your FlyMyAI balance at the price its row
shows.

The current list is on [flymy.ai/mcp](https://flymy.ai/mcp/?category=ready#catalog),
and each connector's page there shows the price of every method. Keenable web
search and page reading are Instant: see the [Keenable MCP](https://docs.flymy.ai/mcp/keenable.md) page.

## Find one

Call `search_tools` with what you need. An Instant row says `ready: true` and
`access: platform_key`, and carries its `price`:

```text
search_tools({"query":"web search"})
```

| Field | On an Instant row |
| --- | --- |
| `ready` | `true`: it runs now, with no setup |
| `access` | `platform_key`: FlyMyAI's key runs it |
| `price` | USD per `unit` (`call` or `second`); `kind` is `free`, `fixed` or `variable`; `unknown` means no price card yet, not free |

A connector whose key FlyMyAI does not hold shows `access: setup_required`
instead. Some actions of an Instant connector touch data of one provider account
(history, usage, stored results), which a key shared by every user must never
read, so they run only on a key of your own and say so in their description.

## Call it

Read the exact arguments with `get_tool_schemas`, then call `execute_tool` with a
new `operation_key` for each intended call:

```text
get_tool_schemas({"runtime_names":["custom--keenable--keenable_search"]})
execute_tool({"tool":"keenable","action":"keenable_search",
  "arguments":{"query":"post-training quantization","max_results":3},
  "operation_key":"keenable-search-<uuid>"})
```

An agent run gets the same action as `custom--<toolkit>--<action>`, and there is
nothing to attach for FlyMyAI's key. A call that FlyMyAI refuses before it runs
(arguments, setup, the provider) says why and changed nothing: fix it and send it
with a new `operation_key`.

## What it costs

Each call is billed to your balance when it finishes: the provider's own price
when the provider charges per request, plus the call's compute time, and never
less than the compute time. A provider with a free allowance adds nothing for its
part while the allowance lasts. A row's `price` is what the platform measured for
that action, and `price` before a paid call is yours to read: `unknown` is not a
promise of zero.

## A key of your own

Optional. Connect your own key in the app (**MCP** > the connector) to run the
connector on your own provider account and plan, or to use the actions that need
one. The connector's page lists which actions those are.
