Loops HouseInferNear

NEAR HACKATHON
Links
Team
1 member- ALOwner
Alvin Yap
Overview
Problem: NEAR AI Cloud runs open models inside attested TEEs, but it is paid for from a NEAR AI account, while most people who want private AI keep their assets and wallets on other chains and do not want API bills to eat their capital.
What we built: InferNear, an OpenAI-format API endpoint (https://api.infernear.dev/v1) for NEAR AI Cloud's private TEE models. Users deposit into vaults on their own chain (Aave USDC, cbETH and Pendle PT ERC-4626 vaults on Base, or a Rhea USDC vault on NEAR), keep their principal, and the yield becomes API credits on a NEAR ledger contract. Credits can also be bought directly with USDC on Base. Users sign in with the wallet they already have (EVM or NEAR) and never need a NEAR account. In private mode NEAR AI's SDK verifies the model's TEE, encrypts the prompt before it leaves the user's machine and checks the signature on the reply, so the relay only carries ciphertext; the console shows this in a Verified panel.
How NEAR fits: NEAR AI Cloud serves every model. NEAR Intents (1Click) carries USDC between Base and NEAR for the Rhea vault. The credit ledger and the Rhea vault are NEAR contracts; credits are posted there and each paid call is debited there under its inference ID. Rhea Lend provides the NEAR-side yield.
Live on mainnet: https://app.infernear.dev (console), https://docs.infernear.dev (docs). Walkthrough video: https://www.loom.com/share/008bb265a87440cca9802d201ba0291f