# Extended (/providers-execution/extended)



Extended execution is introduced in MarketLab **0.1.145**. `extendedf` selects perpetuals; `extended` selects spot. Both obey the workspace network, including `--testnet`.

## Connect an account [#connect-an-account]

In Furge, choose **Accounts → Extended**, then enter the API key and Stark private key for the same Extended subaccount. The account ID and settlement vault are discovered from the authenticated account details. Furge verifies that the Stark public key matches the API key's subaccount before saving anything.

Obtain the credentials from [Extended API management](https://app.extended.exchange/api-management). A Stark key has full authority over its subaccount, including native transfers and withdrawals. Use a dedicated subaccount for the integration. Furge’s adapter and gateway limit their supported actions to trading and account reads.

For a standalone CLI, run the hidden credential prompt:

```sh
mlab auth set extended --agent --account auto
```

Enter a JSON object containing `api_key` and `private_key` at the prompt. Add `--testnet` for Sepolia. Automation can supply the same JSON using `--agent-stdin`; keep it out of command arguments and shell history. Managed runtimes use the existing KMS-backed credential store.

## Funding before connection [#funding-before-connection]

After the API/Stark identity checks, connection reads the selected sub-account’s balance before saving credentials or returning a connected receipt. An empty account shows **Deposit USDC into this Extended sub-account, then try again**, with a link to the matching Extended network and a retry action. Entered keys stay in the form while the user deposits; the connection completes only after the check succeeds.

Extended documents `404` from its balance endpoint as zero balance, and `404` from spot balances as no assets. These exact empty-balance responses require a deposit. Other 404s, authentication errors, malformed payloads and upstream outages do not trigger that message. A positive-equity account can connect even if its free margin is currently zero.

Already-linked empty accounts receive the same funding guidance in Execution. See [Extended’s balance API](https://api.docs.extended.exchange/#get-balance).

## Orders and account state [#orders-and-account-state]

The provider supports market and limit orders, IOC, GTC mapped to Extended's expiring GTT orders, post-only limits on order-book markets, and reduce-only perpetual orders. It checks native minimum base size, tick and lot increments, leverage, settlement asset IDs and account-specific trading fees. Market orders carry a worst accepted price and a short expiry.

Private WebSocket events normalize orders and fills for streaming consumers. Account and position changes can trigger a balance or position refresh. Native trade IDs support deduplication and reconnect recovery.

Delta Neutral and liquidity-hedge runs use authenticated HTTP snapshots and order reconciliation. An accepted order remains pending until the venue confirms its terminal status. The runtime checks exact order history when the immediate lookup has no record and uses the venue’s confirmed average fill price when available.

Native attached TP/SL and OCO submission are not enabled by this adapter. A request for them is rejected explicitly.

## RFQ markets [#rfq-markets]

The catalogue's `isRfq` flag selects the native RFQ order endpoint. RFQ markets do not support post-only quoting, and their resting orders pay taker fees. The adapter paces RFQ submissions per subaccount. The managed gateway shares HTTP, connection and subscription budgets with public indexing, reserves cancellation capacity and honors upstream backoff without replaying signed requests.

The terminal's **Indicative** book remains a reference display. Indicative quotes are never inserted into executable liquidity aggregation. Market makers need order-book markets that support post-only orders.

## Builder fees and recovery [#builder-fees-and-recovery]

Extended’s `builderId` is the builder’s **numeric client ID**, available on the API page after connecting the builder wallet. Set that ID in the node’s fee policy. **Approve and connect** verifies the Stark identity and binds consent to the current policy revision. Each order’s Stark settlement signature includes the maximum exchange and builder fee. [Extended’s builder-code guide](https://docs.extended.exchange/extended-resources/builder-codes).

Submission identities are saved before sending. If delivery is uncertain, recovery looks up the same external order ID instead of replaying a stale signed order. Batches preserve input order and report each result separately.

Books, trades, candle history and volume-derived strategies reuse [the Furge market-data index](/providers-market-data/extended). Configure the matching Extended consumers on that node. Standalone signing and account access use Extended directly; a complete native CLI ticker stream is not advertised.

[Extended API reference](https://api.docs.extended.exchange/).
