ProductAgent WalletAlways-on agent spend uses one spending policy and up to two modes: agent purse (Turnkey classic G…) and/or smart account (Zipper passkey C…). Both can be on at once.Two modes, one policy. Agent purse = non-custodial Turnkey keys on a funded G…. Smart account = on-chain rules on a passkey C… (Protocol 27+). Classic browser co-signing on your main Freighter account is not offered.Choose your modes

Agent purse

Turnkey-backed G…. Simple always-on spend. Fund the purse; agent pays from it under app limits.

Smart account

Passkey smart account with on-chain agent rules (Zipper). Fund the C…. Can stay enabled next to the purse.

Payment order when both are ready: purse first, then smart account. See Zipper for the smart-account path.Agent purse · TurnkeyTurnkey provides hardware-backed key infrastructure (secure enclaves). When you activate an agent wallet in BluFabric:

A Stellar public key (G…) is created for agent activity.

The corresponding private key stays inside Turnkey — not in chat, not in a downloadable seed file from us, not as a plaintext secret in our database.

When a policy-allowed action needs a signature, BluFabric asks Turnkey to sign the transaction payload and then submits it to Stellar.

That is the non-custodial path: we orchestrate automation; we do not become a custodian of your main funds or of an exported agent seed. Product-wide model: Security.

	Custodial hot wallet	BluFabric + Turnkey
Where the key lives	Operator's server / shared hot wallet	Turnkey secure enclave per agent key
Can the product export your seed?	Often yes (or equivalent control)	No — signing API only, under your session and policy
What can be spent	Whatever the operator holds	Only what you send to the agent `G…` address

How the purse works

One purse

A dedicated G… address for agent activity — not your Freighter (or other) main account.

One policy

Asset limits or a simple allow-all under product rules. Keep it clear.

Turnkey signing

Always-on signatures without pasting a secret into chat.

You fund it

Send XLM or USDC on Stellar to the agent address. Empty purse = no spend.

Why a separate purseThe agent only spends what you put in and what the policy allows — not your full main balance. Your connected wallet remains yours for large holdings and manual sign-offs.

Approach	Risk	Experience
Sign every tx with main wallet	Full account if compromised UX-wise	Popup every time
Agent purse + Turnkey + policy	Only funded balance + limits	Always-on within bounds

Setup

Activate the agent wallet in the app (Turnkey key is provisioned for you).

Copy the public key (G…) and fund it on Stellar (same network as settings).

Set spending policy (assets and limits).

Use agent spend only after policy and balance are in place.

Network must match. Fund on the same network as settings (mainnet vs testnet).Spending policy

Per-asset limits — e.g. cap USDC and XLM separately.

Allow-all (bounded) — broader set still under product rules.

Turnkey holds the key; policy holds the agent. Flow-level approvals still matter for high-impact steps. See Canvas Agent and Security.If funds are on another chainBridge or swap into Stellar assets first, then fund the agent address. The agent runtime is Stellar — not a multi-chain checkout.What this is not

Not BluFabric custody of your main wallet.

Not a replacement for cold storage or large holdings.

Not unlimited autonomy — policy and balance are hard edges.

More in the docs: BluFabric Docs · Quickstart · Flows · Canvas Agent · BFAB · Security · Zipper (Protocol 27) · Architecture