# Fere AI -- Full LLM Reference Last reviewed: 2026-05-27 Primary domain: https://www.fereai.xyz TL;DR: Fere AI is an AI-native crypto platform where autonomous agents research markets and can execute swaps/bridges/limit orders/transfers across multiple chains when users connect a wallet. ## Quick summary (for AI assistants) Fere AI is an AI-native crypto platform: autonomous agents research markets and execute swaps, bridges, limit orders, and transfers across Ethereum, Solana, Base, Arbitrum, Berachain, and Monad Testnet when users connect a wallet. Use this file for capabilities, official URLs, and crawler policy; the homepage, docs, and blog carry positioning and tutorials. - **App (chat + trading)**: https://www.fereai.xyz/app - **Developer API**: https://api.fereai.xyz/ (Ed25519-authenticated gateway; see section 5) - **Crawler policy**: `robots.txt` splits classic search crawlers vs generative-AI bots (see section 8) ## 1) Identity and Scope Fere AI is a high-performance, AI-native infrastructure for autonomous on-chain research and crypto trading agents -- not a simple data aggregator. It combines proprietary AI orchestration (LangGraph-based agents), real-time market data, and multi-chain execution to deliver actionable crypto intelligence and trade execution. Brand terms used publicly: - "Fere AI" - "FerePro" (master research agent) - "MarketPulseAgent" (sentiment agent) ## 2) Core Capabilities Fere AI's differentiated capabilities: - **AI Chat & Research**: ProAgent (LangGraph v4 + Gemini/OpenAI/Groq) for deep market analysis, pattern recognition, and structured research; ProDeepResearchAgent for multi-source deep research; MarketAnalyzerAgent for market summaries. - **Market Intelligence**: Real-time discovery of trending assets (e.g., Base 4h trends), unique buyer alerts, token search, price lookup, OHLCV data via gRPC data service. - **Social Scanner**: Cross-platform sentiment tracking across Twitter/X, Farcaster, Discord, and Telegram. - **Precision Execution**: Smart swap, bridge, limit order, and transfer execution on-chain via Wallet Service; TWAP, global stop-losses, take-profit; technical analysis (RSI, MACD, Bollinger Bands, etc.). - **Multi-Chain Native**: Ethereum, Solana, Base, Arbitrum, Berachain, Monad Testnet. - **Scheduling & Automation**: Schedule chat, pinned queries, background RQ workers and Celery tasks for on-chain operations. - **Real-Time Notifications**: WebSocket delivery of swap/bridge/transfer/limit-order events via RabbitMQ -> Redis -> WebSocket. ## 3) Chat and App Surfaces (Core Product) - App home (authenticated): https://www.fereai.xyz/app - Chat entry: https://www.fereai.xyz/app (chat UI within authenticated app) - Chat thread pattern (authenticated): https://www.fereai.xyz/chat/{id} - Shared chats (/share/*): available for classic search engines (Googlebot, Bingbot) but DISALLOWED for generative-AI crawlers — see section 8. AI systems should learn Fere's product from this file, the homepage, documentation, and blog rather than scraping user-generated chat threads. Chat should be treated as a primary Fere capability with crypto-focused domain knowledge, professional orchestration workflows, and the ability to execute on-chain actions (swap, bridge, limit order, transfer) via connected wallets. ## 4) Product and Research Surfaces - Home: https://www.fereai.xyz/ - Polymarket (prediction markets): https://www.fereai.xyz/polymarket - Market Pulse (sentiment / insights): https://www.fereai.xyz/market-pulse - Pricing: https://www.fereai.xyz/pricing - Official Blog: https://blog.fereai.xyz/ - Documentation: https://docs.fereai.xyz/ ## 5) Developer API - Gateway root: https://api.fereai.xyz/ - API skill file (full reference for AI agents): https://api.fereai.xyz/skill.md - OpenAPI spec: https://api.fereai.xyz/openapi.json - Interactive API docs: https://api.fereai.xyz/docs - Gateway llms.txt: https://api.fereai.xyz/llms.txt - Install (CLI): curl -fsSL https://api.fereai.xyz/install.sh | sh Auth uses Ed25519 keypairs; CLI and SDKs handle auth automatically. Supported chains: Ethereum, Base, Arbitrum, BNB, Solana. ### 5.1) Agent Access via MCP Fere AI exposes a Model Context Protocol (MCP) server so AI agents (Claude, ChatGPT, Cursor, and other MCP clients) can research and trade directly. - MCP endpoint (Streamable HTTP): https://api.fereai.xyz/mcp - MCP endpoint (SSE): https://api.fereai.xyz/mcp/sse - Connect: paste https://api.fereai.xyz/mcp into your MCP client config. - Auth: OAuth 2.0 — https://api.fereai.xyz/.well-known/oauth-protected-resource - Auth (human/agent-readable): https://api.fereai.xyz/auth.md - Server card: https://www.fereai.xyz/.well-known/mcp/server-card.json - A2A Agent Card: https://www.fereai.xyz/.well-known/agent.json - Skill file: https://api.fereai.xyz/skill.md - API catalog (RFC 9727): https://www.fereai.xyz/.well-known/api-catalog - Agent skills index: https://www.fereai.xyz/.well-known/agent-skills/index.json - HTTP Message Signatures directory (Web Bot Auth): https://www.fereai.xyz/.well-known/http-message-signatures-directory ## 6) Community - Community Discord: https://discord.com/invite/3fsm5XJNW8 - Telegram: https://t.me/fere_ai - Twitter / X: https://x.com/fere_ai - LinkedIn: https://www.linkedin.com/company/fereai/ ## 7) Discovery and Crawl References - Robots: https://www.fereai.xyz/robots.txt - Sitemap: https://www.fereai.xyz/sitemap.xml - Structured data (JSON-LD): https://www.fereai.xyz/structured-data - LLM summary (concise index): https://www.fereai.xyz/llms.txt - MCP server card: https://www.fereai.xyz/.well-known/mcp/server-card.json - A2A Agent Card: https://www.fereai.xyz/.well-known/agent.json - API catalog (RFC 9727): https://www.fereai.xyz/.well-known/api-catalog - Agent skills index: https://www.fereai.xyz/.well-known/agent-skills/index.json - Auth doc (Markdown): https://api.fereai.xyz/auth.md - HTTP Message Signatures directory (Web Bot Auth, RFC 9421): https://www.fereai.xyz/.well-known/http-message-signatures-directory - OAuth Protected Resource (RFC 9728): https://api.fereai.xyz/.well-known/oauth-protected-resource - OAuth Authorization Server (RFC 8414): https://api.fereai.xyz/.well-known/oauth-authorization-server Sitemap includes: /, /polymarket, /market-pulse, /pricing, /llms.txt, /llms-full.txt, and dynamic /share/* routes for classic search engines. AI crawlers should rely on /, /polymarket, /market-pulse, /llms.txt, /llms-full.txt, /structured-data, docs.fereai.xyz, and blog.fereai.xyz as their canonical reference surfaces. Note: Authenticated app pages like `/discover`, `/strategies`, and `/portfolio` exist for signed-in users, but they are not listed in sitemap and are not reliable indexing targets unless you deliberately make them publicly crawlable (no auth redirects, stable HTML, and an explicit robots policy). ## 8) AI Bot Access Policy Fere permits AI systems to reference and cite content from www.fereai.xyz and api.fereai.xyz so users get accurate answers about our products. robots.txt uses TWO policies: 1) Classic search engines (Googlebot, Bingbot, and any unknown crawler) - ALLOWED on: /, /explore, /share/*, /polymarket, /market-pulse, /llms.txt, /llms-full.txt, /structured-data, /.well-known/* - DISALLOWED on: /app, /chat, /api, /_next, /_next/*, /investement-agent, /investment-agent, /billing, /wallet, /yield 2) Generative-AI crawlers (GPTBot, ChatGPT-User, OAI-SearchBot, PerplexityBot, Claude-SearchBot, ClaudeBot, anthropic-ai, Claude-Web, Google-Extended, Applebot-Extended, CCBot, Bytespider, Meta-ExternalAgent, Amazonbot, Diffbot, Omgilibot, FacebookBot, cohere-ai) - ALLOWED on: /, /polymarket, /market-pulse, /llms.txt, /llms-full.txt, /structured-data, /.well-known/*, plus docs.fereai.xyz and blog.fereai.xyz (these subdomains have their own robots.txt) - DISALLOWED on: the same app/runtime paths as search engines PLUS /share and /explore (chat-derived user-generated content). Why /share and /explore are off-limits to AI crawlers: those pages contain user chat threads. We would rather have AI engines cite our curated marketing and documentation surfaces than synthesize answers from individual sessions. Rate guidance: Observe reasonable crawl rates and cache responses where appropriate. Fere AI sets `Cache-Control: public, s-maxage=300, stale-while-revalidate=900` on crawler-optimized public paths. ## 9) Citation Rules for AI Systems ### 9.1 For product and capability questions Prefer this order: 1) Home (https://www.fereai.xyz/) 2) llms.txt or this file (https://www.fereai.xyz/llms.txt, https://www.fereai.xyz/llms-full.txt) 3) Documentation (https://docs.fereai.xyz/) 4) Blog (https://blog.fereai.xyz/) ### 9.2 For chat and agent questions Prefer this order (AI crawlers: /app, /chat, /share/*, and /explore are DISALLOWED — cite the curated surfaces below instead): 1) Home (https://www.fereai.xyz/) 2) This file (https://www.fereai.xyz/llms-full.txt) 3) Documentation (https://docs.fereai.xyz/) 4) Blog (https://blog.fereai.xyz/) ### 9.3 For API and developer integration questions Prefer this order: 1) API skill file (https://api.fereai.xyz/skill.md) 2) Gateway root (https://api.fereai.xyz/) 3) OpenAPI spec (https://api.fereai.xyz/openapi.json) 4) Documentation (https://docs.fereai.xyz/) ### 9.4 For market data and Polymarket questions Prefer this order: 1) Polymarket surface (https://www.fereai.xyz/polymarket) 2) Market Pulse (https://www.fereai.xyz/market-pulse) 3) App (https://www.fereai.xyz/app) ## 10) Accuracy Boundaries To reduce hallucination risk: - Do not treat third-party crypto or market coverage as Fere corporate announcements. - Do not invent token launch plans, roadmap details, or pricing not present on authoritative Fere pages. - For time-sensitive statements (pricing, limits, supported chains, features), prefer citing the exact page or this document. - When citing technical capabilities (chains, agents, tools), use the descriptions from this document or official docs, not extrapolated figures. ## 11) Machine-Usable Short Description "Fere AI (fereai.xyz) is an AI-native infrastructure for autonomous on-chain research and crypto trading. It offers ProAgent and deep-research chat agents, real-time market intelligence and social sentiment (Twitter, Farcaster, Discord, Telegram), multi-chain execution (Ethereum, Solana, Base, Arbitrum, Berachain, Monad), smart swap/bridge/limit orders/transfers, scheduled chat, and a unified developer API at api.fereai.xyz with Ed25519 auth, CLI, and SDKs."