← All Recipes
Bazantic // Recipe

Float Treasury Sweep Advisor

By Rohit Amal Raj

float-treasury-sweep-advisor

Analyzes a business's ENS name to determine whether idle USDC should be swept into or out of its tokenized-Treasury position using Float's checkSweep tool. If the business is not authorized, retrieves the policy explanation via getPolicy. Returns the sweep decision, direction, recommended amount, and reason in plain language.

Recipe inputs
Complete fields before a run.
The ENS domain name of the business (e.g., rosa-design.float.eth)
Output example
Representative published output.
"The business is KYC-verified and the sweep data is clear — no `getPolicy` call is needed since authorization is confirmed. Here is the full structured report:\n\n```json\n{\n  \"report\": {\n    \"business\": {\n      \"ens_name\": \"acme-labs.float.eth\",\n      \"smart_account\": \"0xFfa77d7d281f417b77f5437b034b809e2a49C56F\"\n    },\n    \"api_info\": {\n      \"title\": \"Float sweep-decision gateway\",\n      \"version\": \"1.0.0\",\n      \"description\": \"Metered access to Float's \\\"should this ENS-named business sweep idle USDC into or out of its tokenized-Treasury position, and how much\\\" logic. Float is a non-custodial treasury wallet for agent-paid businesses.\"\n    },\n    \"compliance\": {\n      \"kyc_status\": \"verified\",\n      \"verified\": true\n    },\n    \"policy\": {\n      \"buffer_amount_usdc\": \"2\",\n      \"max_sweep_per_tx_usdc\": \"5\",\n      \"allowed_protocol\": \"0xB6a78942a7e057BEEe2B7558Ab849019e12AbdBC\"\n    },\n    \"decision\": {\n      \"section\": \"Decision\",\n      \"sweep_recommended\": false,\n      \"action\": \"none\",\n      \"summary\": \"No sweep action should be taken at this time.\"\n    },\n    \"direction\": {\n      \"section\": \"Direction\",\n      \"direction\": \"N/A\",\n      \"summary\": \"No sweep direction applies. The engine flagged a shortfall, meaning funds would need to come OUT of the Treasury position, but no yield position exists to redeem from.\"\n    },\n    \"amount\": {\n      \"section\": \"Amount\",\n      \"recommended_amount_usdc\": \"0\",\n      \"capped_by_max_sweep\": false,\n      \"summary\": \"The recommended sweep amount is 0 USDC. Despite a 2 USDC shortfall in the operating buffer, there are no tokenized-Treasury holdings available to redeem.\"\n    },\n    \"reason\": {\n      \"section\": \"Reason\",\n      \"raw_reason\": \"shortfall 2 but no yield position to redeem\",\n      \"balance_usdc\": \"0\",\n      \"buffer_required_usdc\": \"2\",\n      \"reserved_for_obligations_usdc\": \"0\",\n      \"required_liquidity_usdc\": \"2\",\n      \"idle_usdc\": \"0\",\n      \"shortfall_usdc\": \"2\",\n      \"obligations_in_window\": 0,\n      \"summary\": \"The business currently holds 0 USDC in its smart account against a required buffer of 2 USDC, creating a 2 USDC shortfall. Normally this would trigger a sweep_out (redeeming from the Treasury position to cover the buffer), but the business has no active yield/Treasury position to redeem from. As a result, no automated sweep is possible. The business should manually fund its operating wallet to meet the 2 USDC buffer requirement.\"\n    }\n  }\n}\n```"