Cheap AI inference. Crypto payments. One key.

Download the Python agent client v7 · SHA256

Using the website

Open 1NFER → Create an account → save your key → Register this account. Click Top up next to registration or click the balance in the header. Choose an amount from $1 and an enabled crypto method before clicking Create my invoice and pay its exact network, address and amount. Wait for credited. Copy API key is available in the header and beside registration once your account is open. On another visit, open Account & key and use your saved key. The default session cookie keeps your account open after reload. An encrypted recovery copy of the API key is retained on this browser by default, unless you turn off Remember; this lets you retrieve it later without sending it to our server. Clearing browser site data removes the copy, so keep your own backup too.

Your first useful result, in one clear path

Evaluate a function, draft a concise API example or review a small code snippet. Compare the answer and metered charge before funding a larger workload. A useful result is a reason to return and invite another builder.

Download, register, create an invoice

Download the client and verify the ZIP checksum. Extract it, inspect its scripts, then run these commands. All secrets stay in your private local directory, outside Git.

mkdir -m 700 ~/1nfer-private
python3 scripts/1nfer.py init --key-file ~/1nfer-private/key.json
python3 scripts/1nfer.py register --key-file ~/1nfer-private/key.json
python3 scripts/1nfer.py models --key-file ~/1nfer-private/key.json
python3 scripts/1nfer.py terms
python3 scripts/1nfer.py topup --key-file ~/1nfer-private/key.json --usd 1 --asset XMR --intent-file ~/1nfer-private/topup-1.json

Invited by another builder? Add --referral-code PUBLIC_ACCOUNT_ID to init. It is saved with your registration intent; subsequent registration uses the same key and code.

Pay from your agent's existing wallet

python3 scripts/1nfer.py payment-plan --invoice RETURNED_INVOICE_ID --asset XMR --max-usd 1
python3 scripts/1nfer.py invoice --invoice RETURNED_INVOICE_ID
python3 scripts/1nfer.py account --key-file ~/1nfer-private/key.json

The payment plan contains exact asset, network, address, crypto amount and expiry. It is refused for expired, uncertain or already credited invoices, or when the USD total exceeds your cap. Give the plan to your existing wallet tool only within its operator-approved budget; set a separate network-fee cap. The client never reads wallet secrets, signs or transfers. Recheck the invoice immediately before sending. If a wallet transfer has an uncertain result, reconcile it instead of sending again.

From account to a paid request

1. Download and inspect the client. Use init to save a key to a private local file; register activates that same key.
2. Read models and terms. Choose a supported model and budget for a short text task.
3. Create topup --usd 1 with your saved key and a private intent file. Open the returned same-domain invoice link.
4. Pay only the shown amount/network/address while the invoice is pending and unexpired. XMR uses an integrated address without a separate payment ID. The client does not spend from your wallet.
5. Check the invoice until credited, then account. Use chat --confirm-paid for one explicit paid request. Compare the answer and balance delta.

What the launch tiers actually buy

One confirmed top-up earns the following rate factor. Smaller payments do not combine into a higher tier. No service fee; blockchain fees are separate.

$500 at the 20% tier gives $2,500 of reference-rate inference purchasing power. Your prepaid USD balance is still $500; usage is charged at the lower rates. The interface leads with reference-rate inference credit and shows actual prepaid USD separately, along with your model rates. The monetary ledger is not multiplied. This is API usage credit, not an investment or withdrawable cash. Read current authenticated model prices and the pricing policy. The launch offer may change for future usage; no fixed end date is set.

OpenCode: a ready profile, no key inside

Download the OpenCode provider profile →

1. Merge its provider section into your existing project opencode.json, preserving your other providers.
2. In OpenCode use /connect → Other, provider ID 1nfer, and paste your saved API key privately.
3. Run /models. Choose claude-sonnet-4-6 for function tools; claude-sonnet-5 supports text chat. Start with a small standalone task.

OpenCode stores credentials in its local auth file. The profile follows official configuration; full runtime and tool loops have not yet been verified by us.

Connect existing frameworks

OpenCode: its custom-provider guide supports Chat Completions through @ai-sdk/openai-compatible. Add your privately saved key with /connect → Other, set the endpoint above, and select the exact model from your 1NFER catalogue. For function tools choose claude-sonnet-4-6, the only route where standard tools have been verified.

Hermes: use hermes model and Custom endpoint following the official provider instructions. Supply the endpoint, saved key and exact model. Framework installation and complete tool loops have not been tested by us; the manual client is the tested first step.

Provider-declared input windows are 1M tokens, except Opus5.5 at200k; output maximum128k/default1024, HTTP body16MiB. The small manual CLI limits output to128. Full windows have not been load-tested. No confirmed free generation, vision or Responses API. Use the live per-model limits when planning long sessions. The chat shows the exact selected model and your current input/output rates before sending. Exact named requests are not silently replaced; SSE is buffered.

A useful result is worth sharing

python3 scripts/1nfer.py referrals --key-file ~/1nfer-private/key.json

Get your own public invitation and anonymous registration/funding counts. Share a tested use case with another builder: your exact model, task, observed cost and limitations, plus your invitation. The link contains your public account ID, never your API key. Referral rewards are not enabled.

“I tested 1NFER on [task] using [model]. My observed cost was [charge]. Try your own small task from $1; the current $100 launch tier charges 30% of eligible listed reference rates. Here is my invitation: [public URL].”

The strongest recommendation is one the next agent can reproduce. No earnings, traffic or quality outcome is guaranteed.

Pay from your wallet or an exchange

New invoices do not request a sender wallet. ETH, TRX and USDT/TRC-20 use a single-use receiving address, with public-only watch wallets on our private Bitcart backend. Send the exact displayed asset and amount on the correct network; include your exchange or wallet fee separately. Keep the invoice and transfer reference, then wait for confirmed account credit. Old invoices retain their original verification requirements.

Verified payments, private access

Our owner-controlled $1 Monero test reached Bitcart complete, one account credit, a Sonnet5 answer and a matching usage deduction. Other configured currencies still await live transfer tests. The invoice keeps a receipt after funding. A public invoice URL cannot sign you in: use your saved API key to view balance. Seed/spend keys stay in your wallet, not in our checkout.

Propose a larger budget to your operator only when the task, model, rates and expected usage justify it. Router/bot setup is a separately agreed service: HESOYAM turnkey setup. Customer demand, earnings and traffic are not guaranteed.

Create your key and start with a small test →