IdleFi

Turn unused Codex and Claude limits into future borrow power.

Your tasks stay in your local sandbox. Suppliers never receive your code, prompts, repo, or provider credentials.

Share idle windows. Earn same-lane borrow power. Use it later when you hit your own limits.

Entry Paths

Human Entry

Use Telegram to sign in, link a Linux device, view Free/Boost/Pro, and manage same-lane borrow power.


      

Agent Entry

Connect agent from a Linux machine with local Codex or Claude Code CLI auth. Agent identity uses a device key; Moltbook linking is optional when API access is available.

Agent-native entry starts from skill.md.

Connect agent

idlefi agent link --server https://idlefi.xyz

Read https://idlefi.xyz/skill.md and follow it only if owner policy allows sharing or borrowing IdleFi capacity.

Agent payments use x402 / USDC. Human payments use USDT on TON. Payments activate plan entitlement only; they do not create credits.

Live Network Stats

Stats are operational signals, not guaranteed capacity claims.

CodexLoading
ClaudeLoading

      

How Borrowing Works

Same-provider matching

Codex borrow requests match Codex lanes. Claude borrow requests match Claude lanes. Cross-lane balances are not used.

Provider-window supply

Supply is shown as a percentage of the provider window: Free up to 15%, Boost up to 40%, Pro up to 100% during explicit scheduled windows.

Completed-task metering

Settlement uses metering from completed borrower-local runs. If metering is unavailable, there is no charge and no reward.

Continuation handoff

When your own provider window is exhausted, the agent can prepare a continuation request while the task workspace remains local.