Documentation

Build a clear view of Robinhood Chain.

Learn how Rynora queries public chain data, what each research module supports and how to configure the deployment safely.

Current release1.0

Live network, wallet, token, radar, news and optional AI explanation modules.

Overview

Rynora AI documentation

Rynora is an AI-native intelligence interface for Robinhood Chain. It combines natural-language questions with public explorer and RPC data. The current website includes working network status, address analysis, token research, recent activity radar, dynamic news cards, wallet connection and a configurable token page.

Evidence principle

Blockchain facts come from network data functions. AI, when enabled, receives the verified response and is instructed to explain only that data.

Quickstart

  1. Open the Rynora terminal.
  2. Ask a network question or include a complete EVM address.
  3. Review the answer, metrics and stated limitations.
  4. Open the evidence link in the Robinhood Chain explorer.
Example question
Explain 0xYourWalletAddress and show the available activity counters.

Supported queries

IntentExampleCurrent data
Network statusWhat is the latest block?Block height and explorer counters
Address profileExplain 0x...Balance, type and activity
Token profileAnalyse token 0x...Metadata, holders and transfers
Recent activityShow large transfersCurrent transaction window
Address comparisonCompare 0x... and 0x...Up to three address snapshots

Wallet and contract profiles

Address profiles combine explorer information with a current RPC snapshot when available. The interface may display native balance, account type, transaction count, token transfer count, source-code verification status, creator information and implementation address.

Rynora does not infer a real-world identity or claim that two addresses are related.

Token profiles

Token research uses the contract address as the starting point. Names and tickers can be duplicated, so users should compare the contract against authoritative registries and explorer records.

Displayed fields depend on what the explorer reports. Missing verification, price or holder data should not be interpreted as a risk conclusion.

Live radar

The radar displays a current public explorer window, including recent transactions, visible native-value transfers, contract interactions and blocks. It is not a complete historical market ranking.

News feed

The news endpoint retrieves metadata from a controlled list of official or established ecosystem sources. Each card links directly to the original publisher. If a source cannot be reached, Rynora displays its curated fallback summary and branded image.

Site configuration

Public brand links, network details and token information are managed in config.json. When the official token contract is ready, replace the placeholder value with the complete EVM contract address.

config.json
{
  "token": {
    "ca": "0xYOUR_CONTRACT_ADDRESS",
    "buyBaseUrl": "https://www.ponsfamily.com/launchpad/"
  }
}

The website then displays the official contract and activates the appropriate token links.

Server environment

.env
ROBINHOOD_RPC_URL=https://robinhood-mainnet.g.alchemy.com/v2/YOUR_KEY
OPENAI_API_KEY=
OPENAI_MODEL=gpt-5-mini
BLOCKSCOUT_API_URL=https://robinhoodchain.blockscout.com

Keep API keys in the server environment. Never place private RPC keys or AI keys in client-side JavaScript or config.json.

Security model

  • Strict response headers and a content security policy are included in vercel.json.
  • API routes validate methods, payload size and EVM address formats.
  • Server requests use timeouts and controlled external domains.
  • AI keys remain server-side and model responses are not stored by the application.
  • Wallet connections use the provider already installed in the user’s browser.
  • No seed phrase or private key should ever be requested.