High Priority
Deploy /crypto-ai.txt Protocol
Establish a machine-readable summary of your entire portfolio structure and key asset information specifically for AI agents and LLM crawlers analyzing financial markets.
Create a text file at /crypto-ai.txt with a brief overview of your investment thesis and asset classes.
Include markdown-style links to your most critical performance reports, market analysis pages, and tokenomics documentation.
Add a 'Key Metrics FAQ' section in the file to answer common AI queries regarding your holdings, risk profiles, and yield strategies directly.
Configure your Crypto investing crawler protocols effortlessly.
Join 2,000+ teams scaling with AI.
High Priority
AI Agent Selective Indexing
Fine-tune which sections of your crypto-investment analysis and portfolio data should be ingested by specialized financial AI crawlers.
User-agent: CryptoAI_Bot Allow: /portfolio-performance/ Allow: /tokenomics/ Disallow: /trading-history/
Verify your crawler permissions using a sandbox environment that simulates financial AI bot behavior.
Monitor crawl frequency in your server logs to ensure AI agents are accessing only approved, relevant financial data nodes.
Medium Priority
Semantic Portfolio Structure
Use semantic HTML5 landmarks and structured data (Schema.org) to help LLM scrapers understand the hierarchy and financial significance of your portfolio components.
Wrap your primary investment strategy explanations in <article> tags to signal core content.
Use <section> with descriptive 'aria-label' attributes (e.g., 'DeFi Allocation', 'NFT Portfolio') for distinct asset classes.
Ensure all quantitative data, such as yield percentages and market caps, uses proper `<table>` with `<thead>` and `<tbody>` for structured data extraction.
High Priority
RAG-Friendly Financial Data Chunks
Structure your financial analysis and portfolio data so it can be easily 'Chucked' by Retrieval-Augmented Generation (RAG) pipelines for accurate AI-driven insights.
Keep related financial metrics and performance data within logical data containers, ideally under 750 words per chunk.
Avoid 'contextual drift'; repeat the primary asset or strategy name in section summaries and key data points.
Eliminate ambiguous pronouns and ensure all numerical data is explicitly tied to its corresponding asset, time period, and unit (e.g., 'ETH 24h ROI', 'SOL Market Cap').
