Orient yourself across research, actionable calls, commentary, billing, and support. This hub also explains how content you publish from the admin console surfaces to visitors—not as legal advice but as operational clarity.
Blog: /resources/blog is a server page that calls your API at /blogs (featured + latest). Admin-published posts replace the carousel and lists when the CMS returns rows; errors or empty data show curated showcase posts from the frontend until live content exists.
Research reports: VisiboReportsList on /resources/research loads GET /reports (limit ≈50, LONG_TERM plus optional category/search). Rows reflect admin fields—title, slug, featured, dates, categories, tags mapped to BUY/SELL/HOLD—and refresh on a short React Query stale window (~5 minutes) after publish.
Stock calls: /services/stock-calls embeds HoldingsTable, which loads GET /stock-calls/public when logged out or GET /stock-calls when signed in—with category & search params. Guests see demo sample cards only if the public API returns nothing; authenticated users see catalog calls from Admin → Stock calls after publish.
Homepage (/): intentionally static hero + sections—no inlined “live CMS ticker.” New research and desk calls surface through Resources / Services routes, Navbar, Pricing, Dashboard, or any external lifecycle emails you configure.
Each report states the investment horizon, key assumptions, and valuation approach. Check the publication date before acting—markets may have moved.
Use peer tables, scenario sections, and risk checklists as prompts for your own diligence rather than a single source of truth.
We combine written research with optional community programs and explainers. Participation rules, moderation standards, and premium channel access are described at signup.
Successful payments unlock entitlements when the payment gateway confirms capture. Pro-rated upgrades or cross-grade rules follow the policy communicated at checkout and in invoices.
Retain PDF invoices for bookkeeping; GST-specific fields print when applicable.
Scraping bulk content, circumventing DRM or paywalls, resharing gated PDFs publicly, or using automated bots against our APIs without contract breaches our terms and may lead to suspension.