Live now
The problem
An AI assistant that can pay is one prompt injection away from paying the wrong person. A rule written in the system prompt (“never send more than X”) is advice to the model, not a limit: a malicious email, calendar invite or web page can talk the model out of it. And an AI that reads your private email should not leak it to the infrastructure it runs on. HelloNear’s answer is to take the limits out of the model and make the model’s work verifiable:- Every payment asks the owner, in the app or in Telegram, unless the owner turned on a rule for small payments to listed addresses. Without an approval or a rule, the payment tool cannot run.
- The wallet enforces its own policy. Each Mind’s wallet is an OutLayer wallet whose policy (per-payment limit, daily limit, allowed recipients) is stored on NEAR and checked in a TEE before anything is signed. A payment over the limit or to an unknown address is refused even if the owner approved it, and no transaction exists.
- Freeze. One transaction, signed in the owner’s own NEAR wallet, stops everything.
- Private, verifiable inference. Every model call runs on NEAR AI Cloud inside a TEE. HelloNear checks each reply’s signature against the hardware attestation before it shows the “Verified” badge, keeps that proof, and lets anyone open it on Phala’s TEE Attestation Explorer.
Where to go next
- Quickstart: try it in two minutes as a guest, or drive it with curl.
- Minds and templates, Skills and tools, Wallet, limits and approvals: the core ideas.
- API reference: every route, from the OpenAPI spec.
- Trust Center: what protects your data and funds, each claim with a link you can check.
For AI agents
This site is readable by machines: /llms.txt lists every page, /llms-full.txt has them all in one file, any page is available as Markdown by adding.md to its path, /skill.md describes what an agent can do with HelloNear, and a search MCP server answers at /mcp. The site is hosted on Mintlify, which generates all four from these pages.