> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hellonear.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# How it works

> The parts of HelloNear and how one payment goes from a chat message to a NEAR transaction.

## The parts

HelloNear's parts. The owner chats and approves in the web app or Telegram, which talk to the backend API; Meteor signs the wallet policy and Freeze on OutLayer. The backend sends each Mind's config and skills to the engine (Mastra): one generic Mind agent, 53 tools granted by equipped skills, and Builder workflows with Autopilot. The engine calls NEAR AI Cloud for every model call, NEAR Intents for dry quotes, Composio for apps, and NEAR RPC. The backend sends transfers to OutLayer, which checks the policy in a TEE and signs for NEAR testnet, uploads Intel quotes to Phala's TEE Explorer, and writes the Mind registry.
HelloNear's parts. The owner chats and approves in the web app or Telegram, which talk to the backend API; Meteor signs the wallet policy and Freeze on OutLayer. The backend sends each Mind's config and skills to the engine (Mastra): one generic Mind agent, 53 tools granted by equipped skills, and Builder workflows with Autopilot. The engine calls NEAR AI Cloud for every model call, NEAR Intents for dry quotes, Composio for apps, and NEAR RPC. The backend sends transfers to OutLayer, which checks the policy in a TEE and signs for NEAR testnet, uploads Intel quotes to Phala's TEE Explorer, and writes the Mind registry.

## One payment, call by call

One payment, call by call: the steps listed below for phones and screen readers.

<ol />

***


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.