KEEL / DOCUMENTATION
How credit comes together.
From a first bond to a lasting record. Understand the rules before you borrow.
01Credit for agents.
KEEL gives software agents access to SOL working capital, with a borrower bond, funded credit lines and an on-chain repayment record. Owners set the spending and repayment permissions; the program enforces the credit rules.
The website introduces KEEL. The separate app is where you register agents, open credit, manage payments and inspect transactions.
- CommitRegister an agent and post its borrower bond.
- UseOpen a funded line and borrow within its limit.
- RepayReturn principal and fee, manually or through authorized Autopay.
A larger line must be earned through qualifying repayment history. Creating an agent or recording a payment does not automatically qualify it for more credit.
02Your first credit line
- ConnectEnter Devnet and connect a Solana wallet with test SOL for the bond, account rent and transaction fees.
- RegisterIn Agents, give your agent a name and role. Registration creates its identity and credit record.
- Post a bondOpen the agent and post 0.01 SOL. The bond remains separate from the lending pool.
- Open a lineRequest a 0.01 SOL treasury line. Available treasury capital and the weekly issuance cap both apply.
- BorrowIn Credit, choose the amount and a 7-, 14- or 30-day term. Review the total, then sign.
- Set repaymentRepay from a wallet or authorize Autopay with explicit per-loan and total limits.
You do not need to deposit your own lending capital to request the treasury’s first line. The borrower bond and the treasury’s backing serve different purposes.
One owner wallet can have one active credit line. Registering another agent under that wallet does not create another allowance. Temporary Devnet wallets are lost on reload or disconnect; use a wallet extension for continued access.
03Limits that grow with history
| First line | 0.01 SOL, backed by treasury capital and secured by a 0.01 SOL borrower bond. |
| Next tier | 0.05 SOL. Requires three qualifying repayments, at least 14 days since enrollment and a credit-record score of at least 100. |
| Qualifying repayment | A loan of at least 0.01 SOL, held for at least seven days and repaid on time. Self-backed loans and instant repayments do not qualify. |
| Assessment | Uses capital at risk over time, qualifying repayments, current backing, record age and late repayments. Scores range from 0 to 900. |
| Treasury capacity | Each approved line locks equal sponsor capital. Current treasury issuance is capped at 0.1 SOL per seven-day period; repayments do not reset that cap. |
| Terms and fee | 7, 14 or 30 days. The fixed fee is 1% per 30 days, prorated by the selected term and rounded up to one lamport. The full term fee applies to early repayment. |
| Bond release | Close the line and repay any loan first. The bond has a four-day minimum hold. A new line for the same owner has a seven-day cooldown. |
| Default | After the due time plus three days, settlement uses the bond first. Uncovered principal reduces sponsor capital. The agent and owner wallet are blocked from new managed credit. |
A 0.01 SOL loan for seven days has a 0.000023334 SOL fee, making the repayment 0.010023334 SOL before network fees.
The first bond covers the initial principal. A larger line exposes treasury or sponsor capital to loss. A score is a record of activity, not a promise of repayment. Wallet-level restrictions cannot prevent one person from using multiple unrelated wallets.
Earlier agents must repay and close their old lines before enrollment. Their repayment counts stay visible, but qualifying history begins with the new credit record.
04Payments, execution & Autopay
Execute within a budget
The agent SDK requests an API quote and checks the caller’s price and borrowing caps. It uses wallet funds first. If the wallet is short and eligible credit is available, it borrows the shortfall and pays in one atomic transaction. If payment fails on-chain, that borrowing also rolls back.
The included paid service returns a snapshot of an agent’s on-chain credit record. It is a working API integration, not a general-purpose AI model or a marketplace of tasks. Other tools and services need their own integrations.
Record actual payments
Each customer payment creates a unique receipt tied to the payer, service agent, amount and quoted result. A completed purchase can retrieve the same result again without paying twice. Payments from the service owner or its sponsor are rejected.
Received payments are gross SOL receipts, not verified profit. Payments from related third-party wallets and circular transfers cannot be ruled out by the receipt alone. Receipt totals do not increase the credit score or borrowing limit.
Repay with permission
Customer payments enter the agent’s Autopay reserve. The owner chooses either repayment from six hours before the due time, or repayment as soon as the reserve covers the full debt. Authorization has both a per-loan maximum and a total budget; it can be revoked.
A keeper submits eligible repayments. It cannot change the recipient, exceed the permission or pull funds from the owner’s wallet. If the reserve is short, the loan remains unpaid. The owner can fund or withdraw unused reserves and can always repay the loan directly.
Autopay requires an active keeper and sufficient reserve funds. It does not guarantee repayment or force off-platform revenue through KEEL. The current payment adapter uses KEEL’s native-SOL format; it is not an x402-compatible endpoint.
05Where the capital comes from
The intended source of lending capital is pump.fun creator fees from the KEEL token. Collected fees can be deposited into the credit pool and assigned to eligible agents.
- CollectCreator fees are claimed into the project treasury.
- AllocateDeposited treasury funds back approved credit lines.
- RecycleRepaid principal becomes available for further lending.
Only funds actually collected and deposited can support credit. Unclaimed fees, projected trading volume and token market value are not lending capital. The trading liquidity pool remains separate from KEEL’s credit pool.
The treasury credit policy is implemented on Devnet. Automated pump.fun fee collection is not connected yet; today’s test pool is funded with Devnet SOL.
The token and the program
The KEEL token and the Solana lending program are separate. Token CA: 5RYRKmUSWUNJtkh3e1jHd6wZpC7L1kgJ3479LLV1pump. A program ID is not the token CA.
Holding the token does not automatically grant credit, a share of fees or a claim on treasury funds. No staking rewards, holder yield or revenue distribution are promised.
06Choose your network
The app starts on Devnet with three choices: Enter Devnet, Enter Mainnet and Read docs. Devnet uses test SOL and real on-chain transactions.
Enter Mainnet opens the launch screen. Its three-hour countdown uses one shared opening time, so refreshing the page does not restart it. Mainnet transactions stay unavailable until both the countdown and release checks are complete. Use the network selector to return to Devnet.
Devnet balances, bonds and credit history do not transfer to mainnet.
07Understand the boundaries
The current release implements bonded credit, deterministic assessment, payment receipts, bounded API execution and authorized repayment on Devnet. The program remains upgradeable.
The first line is a small, bond-covered starting point. Larger lines carry a real risk of loss for their backers. A public repayment record and a signed payment do not establish a borrower’s identity or guarantee future income.
The live transaction checks cover the normal credit lifecycle and rejection cases. Long-duration cases—seven-day qualification, bond release and overdue default—are also tested with explicitly controlled time and history on a local validator. They are not presented as weeks of elapsed Devnet operation.
Mainnet release, independent security review and the creator-fee collection connection remain separate work. No returns or fee revenue are guaranteed.