# Borrow against your holdings to fund agent work _By Nakul Kelkar, September 28, 2026_ ## The funding decision belongs to the owner A business may have money tied up in holdings while its agents need to pay for research, model calls, and compute today. Selling an asset and moving the proceeds into an operating account is one way to fund that work. Borrowing against eligible holdings is another possible arrangement, with a repayment obligation and risks of its own. The Vaaya experience described here is **Coming soon**. We are using the plain description “borrow against your holdings” while the product name is under review. This is a preview of the intended workflow. It does not announce eligible assets, rates, borrowing limits, or a launch date. The useful design question is how that funding would reach an agent without giving the agent authority over the whole treasury. A business owner could approve a source of funding, then give each agent a smaller budget for a defined job. The agent would buy the tools needed for that job through Vaaya. Those are two separate decisions, and the interface should keep them separate. ## A credit facility and an agent key answer different questions Borrowing capacity describes what an account may be able to draw under an agreement. A spending limit describes what a particular agent is allowed to use. Increasing the first should never silently increase the second. Think about an employee with a company card. The company may have a substantial credit facility, while the employee has a small travel allowance. A new company credit limit does not authorize the employee to book a more expensive trip. The owner still sets the purpose and the allowance. The same separation belongs in an agent-run business. A research agent could have a weekly budget for search and data. A coding agent could have a different budget for models and compute. Neither needs access to the terms of a borrowing agreement, the ability to pledge assets, or permission to raise its own limit. Vaaya already has controls for individual agent keys, including spending ceilings, allowed tool types, and pause. [The corporate-card model for agents](/blog/your-agents-need-corporate-cards) explains those controls. Using holdings to support the account's funding is the coming-soon part of this post. ## A hypothetical draw should remain visible as debt Consider a fictional agency planning a week of client research. The owner approves a $120 research budget and funds it through a hypothetical borrowing facility. These numbers illustrate bookkeeping only; they are not Vaaya terms, a borrowing quote, or a customer result. The owner gives one research agent a $40 weekly ceiling. The rest of the approved budget stays outside that agent's permission. The agent spends $12 on supported tools and returns its work with a record of the charges. Three numbers now need separate treatment: the amount borrowed, the amount the agent was allowed to spend, and the amount actually spent. A $12 tool bill does not prove that only $12 was borrowed. An unused agent allowance does not prove that debt was repaid. The owner needs the facility's actual draw and repayment records alongside the tool charges. A sensible workflow would show when the borrowing occurred, the remaining obligation under its terms, and the charges attributed to each agent. It would also keep a record of who approved the budget. The proposed borrowing experience should make those relationships inspectable before anyone relies on it for operating cash. ## Repayment needs its own plan An agent can finish useful work before the business receives money from a client. It can also spend its budget on work that never produces revenue. Completion of the task therefore cannot be the repayment plan. The owner needs to know which cash will meet the obligation, when it will arrive, and what happens if it arrives late. Existing commitments matter too. Money expected from one invoice cannot simultaneously cover payroll, a supplier, and a borrowing repayment. Collateral can change in value while the debt remains outstanding. In its [explanation of securities-backed lines of credit](https://www.finra.org/investors/insights/securities-backed-lines-credit), FINRA describes how a decline in collateral value can lead to a demand for additional collateral or repayment, and potentially a sale of pledged securities. That is general background about those lending arrangements, not a statement of future Vaaya terms. Any Vaaya launch would need to make the actual agreement clear. The reader should be able to identify the lender, costs, repayment requirements, eligible holdings, valuation rules, and what can happen to pledged assets. A spending dashboard cannot substitute for those terms. ## Keep existing credit distinct from this preview Vaaya's existing GitHub-based credit line uses a developer profile. It is a different product mechanism from the coming-soon holdings-based borrowing experience described here. Connecting GitHub does not mean you have pledged investments, and this post does not change the terms shown in your account. Prepaid funds are another distinct choice. Loading money for tools and borrowing money for tools create different obligations, even when the agent uses the same catalog afterwards. The owner should make that funding choice before assigning the agent its task. Our [treasury-management guide](/blog/treasury-management-agent-run-business) starts with operating needs, reserves, and the money available for agent work. Borrowing would fit into that planning process as a funding decision to evaluate, with its cost and risk visible. It should never become the default response when an agent runs out of budget. ## Set the agent's permission independently The part you can do today is define what each agent may spend from the account it already uses. Choose a positive ceiling, select the right period, and allow only the tool types needed for the job. Review the resulting charges before expanding its scope. Open [Agents](/agents) and set a spending ceiling for one agent before its next paid task. ## Questions **Can I borrow against my holdings on Vaaya today?** This borrowing experience is Coming soon. This post describes the intended workflow, not an available offer. Eligible holdings, terms, availability, and a launch date have not been announced here. **Is this the same as Vaaya's GitHub-based credit line?** No. Vaaya's existing GitHub-based credit line is based on a developer profile. The coming-soon concept described here would use eligible holdings to support borrowing. Agent spending permissions remain a separate decision in either case. **Would more borrowing capacity automatically raise an agent's spending limit?** It should not. Account funding and an agent's authorized budget are separate. Vaaya already supports spending ceilings for individual keys; the owner should review any change to those ceilings independently of available account credit.