#llmsmap.me

Independent technical audit

docs.luxalgo.com

docs.luxalgo.com

Overall AI readiness score

A combined result across all audit signals.

85of 100Excellent
AI readiness audit: 10/6/2026Public technical data

Overall AI readiness assessment

How ready docs.luxalgo.com is for AI systems

85/100

Docs (docs.luxalgo.com) received an AI-readiness score of 85/100 in an automated technical audit. llms.txt was accessible, llms-full.txt was accessible, and ai.txt was not found. The robots.txt analysis found 0 explicitly allowed and 0 blocked AI crawlers, with 1 declared sitemap. Homepage markup completeness was 50%; no Schema.org types were detected and 5 OpenGraph tags were detected. Results reflect the public site response observed on 2026-10-05T22:19:50.091Z.

Audit context

llms.txt is accessible and contains 6,525 tokens. An expanded llms-full.txt is also available with 381,345 tokens, giving agents more direct context. No separate ai.txt policy was detected; it is optional, but can clarify training, retrieval, and attribution preferences.

robots.txt is available. 11 of 11 tracked AI bots are not blocked. Declared sitemaps: 1. No Schema.org type was detected on the homepage. 5 OpenGraph tags were found and markup completeness is 50%, leaving more entity interpretation to crawlers.

The mobile Lighthouse profile adds Performance 69/100, Accessibility 97/100, Best Practices 96/100, SEO 100/100, and experimental Agentic Browsing 100/100. These signals have a limited weight: they complement rather than replace llms.txt, robots.txt, and structured-data checks.

Confirmed strengths

  • Accessible llms.txt
  • Expanded llms-full.txt
  • 1 sitemap declaration
  • Strong Google agentic signals

Priority improvements

  1. 1Add JSON-LD for the organisation, website, and core entities.
  2. 2Complete OpenGraph and canonical homepage metadata.
  3. 3Reduce mobile rendering delay and main-thread work.
llms.txt tokens6,525
llms-full.txt tokens381,345
ai.txt
sitemap.xml

Google Lighthouse technical profile

A mobile Lighthouse measurement. Google’s experimental Agentic Browsing category is explained separately and does not replace the broader llmsmap AI-readiness score.

Mobile · Lighthouse
69

Performance

97

Accessibility

96

Best Practices

100

Technical SEO

100

Agentic Browsing

What these results mean

Mobile performance is 69/100, with the largest visible content block appearing in 8.9 s and the browser main thread blocked for 260 ms. Layout shift was 0. The main thread is where the browser runs JavaScript, calculates layout, and paints the page; long work there delays both user input and browser-agent actions.

Accessibility scored 97/100, Best Practices 96/100, and technical SEO 100/100. The experimental Agentic Browsing category scored 100/100. It measures signals Google currently tests for software agents and is shown separately from the llmsmap AI-readiness score.

1

Free the main thread and accelerate the first view

Split long JavaScript tasks, defer non-critical scripts and styles, and shorten blocking request chains. This helps the primary content appear sooner and makes controls usable earlier.

2

Reduce code that loads without helping the page

Remove unused CSS and JavaScript, load heavy widgets on demand, and limit third-party scripts. Less code means less parsing and background work on the device.

3

Make controls unambiguous

Give buttons and links accessible names, associate labels with fields, and use ordered headings and semantic regions. The same structure helps screen readers and software agents understand actions.

FCP1.5 s

First content

LCP8.9 s

Main content

CLS0

Layout stability

TBT260 ms

Blocking time

SI3.0 s

Visual speed

Metric glossary
FCP · First content
When the first text or image appeared on screen.
LCP · Main content
When the largest visible element in the first viewport rendered.
CLS · Layout stability
How much content shifted unexpectedly while loading; lower is better.
TBT · Blocking time
How long the browser main thread could not respond quickly to input.
SI · Visual speed
How quickly the visible viewport filled with content.
10/6/2026Lighthouse 13.5.0Mobile profile

AI readiness checks

Machine-readable files, crawler policy, discovery, and homepage markup.

llms.txt

File found and accessible

https://docs.luxalgo.com/llms.txt
llms-full.txt

Full version is available

https://docs.luxalgo.com/llms-full.txt
ai.txt

ai.txt file was not found

Sitemap in robots.txt1

1 sitemap found

Schema.org (JSON-LD)

Schema.org markup was not found on the homepage

OpenGraph50%

5 OG tags found

AI bot access

Based on robots.txt analysis

GPTBotNot mentioned
OAI-SearchBotNot mentioned
ChatGPT-UserNot mentioned
Google-ExtendedNot mentioned
ClaudeBotNot mentioned
Claude-SearchBotNot mentioned
Claude-UserNot mentioned
BytespiderNot mentioned
CCBotNot mentioned
PerplexityBotNot mentioned
Perplexity-UserNot mentioned

Sitemaps

Declared discovery routes for crawlers and agents.

OpenGraph tags

Social preview metadata found on the homepage.

Markup completeness: 50%
og:titleDocs | LuxAlgo
og:descriptionOpen Vela by LuxAlgo, the next-generation charting platform, save a layout, and build indicators and strategies with Quant, our coding agent.
og:urlhttps://docs.luxalgo.com/platform/getting-started/introduction
og:typearticle
# LuxAlgo

> LuxAlgo is the company behind Vela (https://vela.luxalgo.com/chart), the next-generation charting platform, with Quant, our coding agent, built in, and the largest indicator library in trading. This site documents the platform under https://docs.luxalgo.com/platform, Vela's open-source core, the charting library behind Vela (https://velacharts.dev), under https://docs.luxalgo.com/vela, and PineTS, our open-source Pine Script® runtime, under https://docs.luxalgo.com/developers/pinets.

# Docs

- Get Started
  - [Quickstart](https://docs.luxalgo.com/platform/getting-started/introduction): Open Vela and learn the platform in minutes.
  - [What Is LuxAlgo?](https://docs.luxalgo.com/platform/getting-started/what-is-luxalgo): State-of-the-art charts with Vela, Quant, our coding agent, built in, and the largest indicator library in trading.
  - [FAQ](https://docs.luxalgo.com/platform/getting-started/faq): Get answers to frequently asked questions including how to get access, product questions, and everything you need to know about billing.
- Vela
  - [Overview](https://docs.luxalgo.com/platform/charts/introduction): Set up a chart: layouts, symbols, timeframes, chart types, and settings.
  - [Replay Mode](https://docs.luxalgo.com/platform/charts/replay): Study chart history one candle at a time, at your own pace.
  - [Drawings](https://docs.luxalgo.com/platform/charts/drawings): Draw on the chart: toolbar groups, magnet snapping, and the radial wheel.
  - [Indicators](https://docs.luxalgo.com/platform/charts/indicators): Add indicators from Basic, Orderflow, the LuxAlgo Library, or My Scripts, star favorites, and save templates.
  - Strategies
    - [Strategies](https://docs.luxalgo.com/platform/charts/strategies): Run strategy scripts on the chart and review the backtest overlay.
    - [Performance](https://docs.luxalgo.com/platform/charts/strategies/performance): Read the overall results and see when and where the strategy made or lost money.
    - [Trades Analysis](https://docs.luxalgo.com/platform/charts/strategies/trades-analysis): Understand the size, frequency, and duration of winning and losing trades.
    - [Trades Log](https://docs.luxalgo.com/platform/charts/strategies/trades-log): Inspect individual trades or switch to a calendar of daily backtest results.
    - [Simulation](https://docs.luxalgo.com/platform/charts/strategies/simulation): Replay your backtest's trades to explore different outcomes and drawdowns.
  - [Data](https://docs.luxalgo.com/platform/charts/data): Where chart data comes from, which markets support order flow, and history limits by plan.
  - [Shortcuts](https://docs.luxalgo.com/platform/charts/shortcuts): All chart keyboard and mouse shortcuts in one place.
  - Order Flow
    - [Order Flow](https://docs.luxalgo.com/platform/charts/order-flow/introduction): Native order-flow chart types and indicators, and which markets they run on.
    - [Footprint](https://docs.luxalgo.com/platform/charts/order-flow/footprint): Footprint chart type and footprint overlays: modes, imbalances, unfinished auctions, and the stat table.
    - [TPO](https://docs.luxalgo.com/platform/charts/order-flow/tpo): TPO (market profile) sessions from candles: chart type and overlay, with full structure options.
    - [Volume Delta](https://docs.luxalgo.com/platform/charts/order-flow/volume-delta): Volume Delta and Cumulative Volume Delta from footprint buy and sell volume.
    - [Volume Profiles](https://docs.luxalgo.com/platform/charts/order-flow/volume-profiles): Volume-at-price profiles for a session, a rolling window, or the visible range.
    - [Volume Tails](https://docs.luxalgo.com/platform/charts/order-flow/volume-tails): Volume tails accumulate buy volume from the low and sell volume from the high of a range.
    - [Trade Count](https://docs.luxalgo.com/platform/charts/order-flow/trade-count): Print-count tools: total trades per bar, buy/sell delta, and the running sum.
    - [Bar Stats](https://docs.luxalgo.com/platform/charts/order-flow/bar-stats): Volume, delta, and trade counts for each candle, in a pane under the chart.
    - [Volume Bubbles](https://docs.luxalgo.com/platform/charts/order-flow/volume-bubbles): Volume Bubbles mark size at price; Delta mode splits each cluster by side.
    - [VWAP](https://docs.luxalgo.com/platform/charts/order-flow/vwap): VWAP Bands from candle volume. Works on every market.
- Quant
  - [What is Quant?](https://docs.luxalgo.com/platform/quant/introduction): Our coding agent. It reads your chart, writes and repairs indicator and strategy code, and runs what you approve.
  - [Making indicators](https://docs.luxalgo.com/platform/quant/indicators): Have Quant write an indicator from a request, a screenshot, or a selected chart region, then plot and repair it.
  - [Making strategies](https://docs.luxalgo.com/platform/quant/strategies): Have Quant write a strategy or convert an indicator into one, then run and backtest it on the chart.
- Workspaces
  - [Overview](https://docs.luxalgo.com/platform/workspaces): Save chart layouts, switch between them, and share a copy of a workspace.
  - [Panels](https://docs.luxalgo.com/platform/workspaces/panels): Keep watchlists and indicator tables alongside the charts in a workspace.
  - Watchlist
    - [Docked view](https://docs.luxalgo.com/platform/workspaces/watchlist): Keep the symbols you follow beside the chart, with live quotes and one click to load them.
    - [Advanced view](https://docs.luxalgo.com/platform/workspaces/watchlist/advanced): Summary metrics, a Price / Financials / News table, sections, and allocation for the open list.
  - Journal
    - [Overview](https://docs.luxalgo.com/platform/workspaces/journal): Log fills, review trades on the chart, and read your P&L and Edge Score.
    - [Accounts](https://docs.luxalgo.com/platform/workspaces/journal/accounts): Add, rename, and delete journal accounts. Broker fills sync daily, or when you Refresh.
    - [Dashboard](https://docs.luxalgo.com/platform/workspaces/journal/dashboard): Equity, Edge Score, daily P&L, drawdown, and the calendar for the selected range.
    - [Trades](https://docs.luxalgo.com/platform/workspaces/journal/trades): Log fills, review a round trip, and see those trades on the chart.
    - [Notes](https://docs.luxalgo.com/platform/workspaces/journal/notes): Daily notes from the column, the Notes page, or a click on the chart.
    - [Breakdown](https://docs.luxalgo.com/platform/workspaces/journal/breakdown): Slice P&L by weekday, hold time, symbol, side, tags, and market.
    - [Compare](https://docs.luxalgo.com/platform/workspaces/journal/compare): Two performances on the same metrics — another account, or the previous period.
- Plans & Billing
  - [Plans](https://docs.luxalgo.com/platform/account/plans): What Free, Essential, Premium, Ultimate, and AI Ultra include, and what they cost.
  - [Monthly credits](https://docs.luxalgo.com/platform/account/credits): How monthly credits work, how many each plan includes, and when they reset.
  - [Billing](https://docs.luxalgo.com/platform/account/billing): Monthly and annual billing, renewals, invoices, payment methods, and plan changes.
  - [Cancel your subscription](https://docs.luxalgo.com/platform/account/cancel): How to cancel a LuxAlgo subscription in the app, and what happens after you cancel.
  - [Refunds](https://docs.luxalgo.com/platform/account/refunds): The 30-day money-back guarantee on your first subscription payment, what it covers, and how to request a refund.

- **Separator**
- Strategy Alerts
  - [Introduction](https://docs.luxalgo.com/platform/ai-strategy-alerts/introduction)
  - [Creating Alerts](https://docs.luxalgo.com/platform/ai-strategy-alerts/creating-alerts)
  - [Notifications](https://docs.luxalgo.com/platform/ai-strategy-alerts/notifications)
  - [Webhooks](https://docs.luxalgo.com/platform/ai-strategy-alerts/webhooks)

# Vela for Developers

> The open-source core of Vela by LuxAlgo

- [Vela for Developers](https://docs.luxalgo.com/vela): Fast, extensible financial charts for the web — a headless core, native WebGL2 renderer, batteries-included workspace, and plugin SDK.
- User
  - [Quickstart](https://docs.luxalgo.com/vela/user/quickstart): Get a candlestick chart on screen, then add a scripting engine and an indicator.
  - [Installation](https://docs.luxalgo.com/vela/user/installation): Install @luxalgo/vela from npm, or load the self-contained browser bundle.
  - [The workspace](https://docs.luxalgo.com/vela/user/workspace): The batteries-included chart app: one chart or a multi-chart grid with shared chrome.
  - [Options](https://docs.luxalgo.com/vela/user/options): Market, display, drawings, settings, and per-indicator options for Vela™ and the workspace.
  - [API Reference](https://docs.luxalgo.com/vela/user/api-reference): The public Vela™ surface — the chart, indicator handles, events, and control facades.
  - [Drawing tools](https://docs.luxalgo.com/vela/user/drawing-tools): Interactive drawing tools, the toolbar, and the chart.drawings API.
  - [Renderer features](https://docs.luxalgo.com/vela/user/renderer-features): Read and change how the chart is drawn at runtime, with no indicator re-run.
  - [Data providers](https://docs.luxalgo.com/vela/user/data-providers): Where candles come from — register providers, resolve symbols, and bring your own.
  - [Scripting engines](https://docs.luxalgo.com/vela/user/scripting-engines): Vela™ ships no engine. Install the Pine addon or write your own against the port.
  - [Examples](https://docs.luxalgo.com/vela/user/examples): Offline static and live examples, plus the in-repo playground.
  - [FAQ](https://docs.luxalgo.com/vela/user/faq): Common questions about engines, offline data, live mode, drawings, and attribution.
- Architecture
  - [Overview](https://docs.luxalgo.com/vela/architecture/overview): One core, three layers, three ports — the shape of Vela™.
  - [Data Flow](https://docs.luxalgo.com/vela/architecture/data-flow): How data moves from the first bar to a live indicator.
  - [Modules](https://docs.luxalgo.com/vela/architecture/modules): The three ports as contracts, the composition root, and how the pieces bind.
  - [Boundaries](https://docs.luxalgo.com/vela/architecture/boundaries): Invariants, the import ACL, capability honesty, and data-handling rules.
  - [Settings rows](https://docs.luxalgo.com/vela/architecture/settings-rows): Declarative settings-row kinds for plugin chart types.
  - Decision records
    - [Architecture Decision Records](https://docs.luxalgo.com/vela/architecture/adr): Architecture Decision Records — why Vela™ is shaped the way it is.
    - [0001 — Neutral model as the cross-layer currency](https://docs.luxalgo.com/vela/architecture/adr/0001-neutral-model-as-cross-layer-currency): The neutral model is the only thing that crosses a port.
    - [0002 — Core owns market data](https://docs.luxalgo.com/vela/architecture/adr/0002-core-owns-market-data): The core is the sole owner of primary market data.
    - [0003 — No default scripting engine](https://docs.luxalgo.com/vela/architecture/adr/0003-no-default-scripting-engine): A bare chart is candles-only; scripting engines are opt-in.
    - [0004 — Enforce layering with an import ACL](https://docs.luxalgo.com/vela/architecture/adr/0004-enforce-layering-with-import-acl): Layer boundaries are enforced by lint, not by convention.
    - [0005 — Core owns user drawings](https://docs.luxalgo.com/vela/architecture/adr/0005-core-owns-user-drawings): Interactive drawings are a core-owned model, not renderer state.
    - [0006 — Workspace composes charts; chrome is a projection of the active cell](https://docs.luxalgo.com/vela/architecture/adr/0006-workspace-composes-charts): The workspace composes charts; chrome is a projection of the active cell.
- Contributing
  - [Setup](https://docs.luxalgo.com/vela/contributing/setup): Clone, install, and run Vela™ from source.
  - [Workflow](https://docs.luxalgo.com/vela/contributing/workflow): Quality gates, the playground, and where a change belongs.
  - [Testing](https://docs.luxalgo.com/vela/contributing/testing): How Vela™ is tested — unit suite, playground, and the quality gate.
  - [Debugging](https://docs.luxalgo.com/vela/contributing/debugging): Hands-on debugging of the core, renderer, and playground.
  - [Plugin SDK](https://docs.luxalgo.com/vela/contributing/plugin-sdk): Chart types, renderer layers, native indicators, and widget contributions.
  - [Adding a Renderer](https://docs.luxalgo.com/vela/contributing/adding-a-renderer): Implement the IChartRenderer port and inject a custom backend.
  - [Adding a Scripting Engine](https://docs.luxalgo.com/vela/contributing/adding-an-engine): Implement the ScriptingEngine port for a new language.
  - [Adding a Data Provider](https://docs.luxalgo.com/vela/contributing/adding-a-data-provider): Implement the DataProvider interface and register it on the chart.
  - [Adding a Drawing Tool](https://docs.luxalgo.com/vela/contributing/adding-a-drawing-tool): Add an interactive drawing tool to the core-owned catalogue.
  - [Adding a UI-kit component](https://docs.luxalgo.com/vela/contributing/adding-a-ui-component): Add a component to the Vela™ UI kit.

# PineTS

- [PineTS](https://docs.luxalgo.com/developers/pinets): PineTS is a TypeScript implementation of the Pine Script language, allowing you to write trading indicators and strategies using TypeScript.

- **Guides**
- [Getting Started](https://docs.luxalgo.com/developers/pinets/getting-started): PineTS is a JavaScript/TypeScript runtime that enables execution of Pine Script indicators in JavaScript environments. It supports two input formats:
- [Initialization and Usage](https://docs.luxalgo.com/developers/pinets/initialization-and-usage): This guide explains how to initialize PineTS and run indicators or strategies with detailed documentation of all available options and return values.
- [Indicator](https://docs.luxalgo.com/developers/pinets/indicator)
- [Syntax Guide](https://docs.luxalgo.com/developers/pinets/syntax-guide)
- [Strategy Namespace](https://docs.luxalgo.com/developers/pinets/strategy)
- [Alerts](https://docs.luxalgo.com/developers/pinets/alerts)
- [Pagination & Live Streaming](https://docs.luxalgo.com/developers/pinets/pagination)
- [Data Providers](https://docs.luxalgo.com/developers/pinets/data-providers): PineTS supports multiple market data providers out of the box. Each provider fetches OHLCV candle data and symbol metadata, which PineTS uses to run your indicators.
- [Using within charts](https://docs.luxalgo.com/developers/pinets/using-within-charts): Display Pine Script indicators and strategies on a Vela™ chart with Vela-PineTS.

- **Architecture**
- Architecture
  - [Architecture](https://docs.luxalgo.com/developers/pinets/architecture)
  - Transpiler
    - [Transpiler](https://docs.luxalgo.com/developers/pinets/architecture/transpiler)
    - [Scope Manager](https://docs.luxalgo.com/developers/pinets/architecture/transpiler/scope-manager): One of the transpiler's most critical jobs is managing variable scope and state persistence across bar iterations.
    - [Transformers](https://docs.luxalgo.com/developers/pinets/architecture/transpiler/transformers): The transformation logic is split into specialized transformers found in src/transpiler/transformers/.
    - [Transpilation Examples](https://docs.luxalgo.com/developers/pinets/architecture/transpiler/examples): This page shows actual transpiler output to help understand the transformation process.
  - Runtime
    - [Runtime](https://docs.luxalgo.com/developers/pinets/architecture/runtime): The runtime environment executes the transpiled code. It simulates the Pine Script execution model where the script runs once for every bar in the dataset.
    - [Context Class](https://docs.luxalgo.com/developers/pinets/architecture/runtime/context): The Context is the central object (usually named $) passed to the transpiled function. It acts as the container for:
    - [Series Class](https://docs.luxalgo.com/developers/pinets/architecture/runtime/series): The Series class is the bridge between JavaScript arrays and Pine Script semantics.
    - [Execution Flow](https://docs.luxalgo.com/developers/pinets/architecture/runtime/execution-flow): The run() method orchestrates the execution.
  - Namespaces
    - [Namespaces](https://docs.luxalgo.com/developers/pinets/architecture/namespaces): PineTS mimics Pine Script's namespacing (ta., math., request.) through modular namespace classes attached to the Context.
    - [Technical Analysis (ta)](https://docs.luxalgo.com/developers/pinets/architecture/namespaces/ta)
    - [Math (math)](https://docs.luxalgo.com/developers/pinets/architecture/namespaces/math): This directory contains the implementation of Pine Script's math. namespace functions. These functions provide standard mathematical operations adapted for time-series data.
    - [Array (array)](https://docs.luxalgo.com/developers/pinets/architecture/namespaces/array): This directory contains the implementation of Pine Script's array. namespace functions. These functions manage dynamically sized arrays, distinct from time-series variables.
    - [Request (request)](https://docs.luxalgo.com/developers/pinets/architecture/namespaces/request): This directory contains the implementation of Pine Script's request. functions, primarily request.security for multi-timeframe analysis.
    - [Input (input)](https://docs.luxalgo.com/developers/pinets/architecture/namespaces/input): This directory contains the implementation of Pine Script's input. namespace functions. These functions handle user inputs/parameters for indicators.
    - [Property-Like Access](https://docs.luxalgo.com/developers/pinets/architecture/namespaces/property-access): This document explains how PineTS handles Pine Script's property-like syntax where namespace members can be accessed without parentheses.
  - Specifics
    - [Specifics](https://docs.luxalgo.com/developers/pinets/architecture/specifics): This section covers specific architectural patterns used to solve complex problems in Pine Script emulation.
    - [Tuple Handling](https://docs.luxalgo.com/developers/pinets/architecture/specifics/tuples): Pine Script supports tuples (functions returning [a, b]). PineTS has a specific architecture to handle this while distinguishing tuples from time-series arrays.
    - [Request Security](https://docs.luxalgo.com/developers/pinets/architecture/specifics/request-security): PineTS creates a strictly Two-Level Hierarchy to prevent infinite recursion.
  - [Debugging Guide](https://docs.luxalgo.com/developers/pinets/architecture/debugging): This guide covers practical debugging techniques for PineTS development.
  - [Best Practices](https://docs.luxalgo.com/developers/pinets/architecture/best-practices): This guide covers common mistakes and recommended patterns when working with PineTS.
  - [Syntax Evolution](https://docs.luxalgo.com/developers/pinets/architecture/syntax-evolution): PineTS is evolving to provide a more unified and cleaner API surface. While older syntax patterns remain supported for backward compatibility, they may trigger runtime warnings.

- **Coverage**
- [Language Coverage](https://docs.luxalgo.com/developers/pinets/lang-coverage): This document lists the features of the PineTS language and their status.
- API Coverage
  - [API Coverage](https://docs.luxalgo.com/developers/pinets/api-coverage): This is a list of all the functions in the Pine Script API and their implementation status.
  - [Input](https://docs.luxalgo.com/developers/pinets/api-coverage/input)
  - [Math](https://docs.luxalgo.com/developers/pinets/api-coverage/math)
  - [Technical Analysis](https://docs.luxalgo.com/developers/pinets/api-coverage/ta)
  - [Array](https://docs.luxalgo.com/developers/pinets/api-coverage/array)
  - [Barstate](https://docs.luxalgo.com/developers/pinets/api-coverage/barstate)
  - [Box](https://docs.luxalgo.com/developers/pinets/api-coverage/box)
  - [Builtin](https://docs.luxalgo.com/developers/pinets/api-coverage/builtin)
  - [Chart](https://docs.luxalgo.com/developers/pinets/api-coverage/chart)
  - [Color](https://docs.luxalgo.com/developers/pinets/api-coverage/color)
  - [Label](https://docs.luxalgo.com/developers/pinets/api-coverage/label)
  - [Line](https://docs.luxalgo.com/developers/pinets/api-coverage/line)
  - [Linefill](https://docs.luxalgo.com/developers/pinets/api-coverage/linefill)
  - [Log](https://docs.luxalgo.com/developers/pinets/api-coverage/log)
  - [Map](https://docs.luxalgo.com/developers/pinets/api-coverage/map)
  - [Matrix](https://docs.luxalgo.com/developers/pinets/api-coverage/matrix)
  - [Plots](https://docs.luxalgo.com/developers/pinets/api-coverage/plots)
  - [Polyline](https://docs.luxalgo.com/developers/pinets/api-coverage/polyline)
  - [Request](https://docs.luxalgo.com/developers/pinets/api-coverage/request)
  - [Runtime](https://docs.luxalgo.com/developers/pinets/api-coverage/runtime)
  - [Session](https://docs.luxalgo.com/developers/pinets/api-coverage/session)
  - [String](https://docs.luxalgo.com/developers/pinets/api-coverage/str)
  - [Strategy](https://docs.luxalgo.com/developers/pinets/api-coverage/strategy)
  - [Syminfo](https://docs.luxalgo.com/developers/pinets/api-coverage/syminfo): Symbol information namespace providing metadata about the current trading symbol.
  - [Table](https://docs.luxalgo.com/developers/pinets/api-coverage/table)
  - [Ticker](https://docs.luxalgo.com/developers/pinets/api-coverage/ticker)
  - [Timeframe](https://docs.luxalgo.com/developers/pinets/api-coverage/timeframe)
  - [Types](https://docs.luxalgo.com/developers/pinets/api-coverage/types)
  - [Constants Audit](https://docs.luxalgo.com/developers/pinets/api-coverage/constants-audit)
  - [Others](https://docs.luxalgo.com/developers/pinets/api-coverage/others)

# Open source

LuxAlgo's open-source projects: code on GitHub (https://github.com/LuxAlgo), project pages on luxalgo.com.

- [PineTS](https://github.com/LuxAlgo/PineTS): Our open-source Pine Script® runtime for JavaScript: it transpiles native v6 or v5 source and runs it in Node.js, the browser, or any JS environment. Pine Script® runs on LuxAlgo through PineTS. License: AGPL-3.0. Page: https://www.luxalgo.com/pinets/
- [pinets-cli](https://github.com/LuxAlgo/pinets-cli): Command-line interface for PineTS: runs Pine Script® indicators from the terminal on live market data or your own JSON datasets. License: AGPL-3.0. Page: https://www.luxalgo.com/pinets/
- [Vela open-source core](https://github.com/LuxAlgo/Vela): The open-source core of Vela by LuxAlgo, the charting library behind Vela, our next-generation charting platform: fast, extensible financial charts for the web with a headless core, a native WebGL2 renderer, a batteries-included workspace, and a plugin SDK. License: Apache-2.0. Page: https://velacharts.dev/
- [Vela-PineTS](https://github.com/LuxAlgo/Vela-pinets): The Pine Script® addon for Vela's open-source core: runs indicator() and strategy() scripts through PineTS, in-process or in a Web Worker, via Vela's public ScriptingEngine port. License: AGPL-3.0. Page: https://velacharts.dev/pine-script/
- [luxalgo-mcp-server](https://github.com/LuxAlgo/luxalgo-mcp-server): The LuxAlgo ecosystem as MCP tools for AI agents: the Library, prop-firm data and the challenge simulator, Market Trackers, Edge Stats, and local read-only broker access. Free and keyless, hosted at https://mcp.luxalgo.com/mcp. License: MIT. Page: https://www.luxalgo.com/mcp/
- [broker-sdk](https://github.com/LuxAlgo/broker-sdk): Open-source broker connectivity for code, apps, and AI agents: accounts, balances, positions, trade history, and performance stats from many brokers and exchanges in one normalized schema. Your keys never leave your machine. License: MIT. Page: https://www.luxalgo.com/broker-sdk/
- [trade-journal](https://github.com/LuxAlgo/trade-journal): The open-source trade journal: broker sync, deep analytics, a P&L calendar, trade replay, daily journaling, and AI reflection. Run it locally, or use it free inside LuxAlgo. License: MIT. Page: https://www.luxalgo.com/trade-journal/
- [trade-relay](https://github.com/LuxAlgo/trade-relay): Self-hosted relay between trading alerts and your broker accounts: it parses a webhook or MCP alert, applies risk rails that are on by default, places the order with your own keys, and records everything locally. License: MIT. Page: https://www.luxalgo.com/trade-relay/
- [prop-firm-sim](https://github.com/LuxAlgo/prop-firm-sim): Prop-firm challenge simulator: Monte Carlo over your trading statistics or trade history and a firm's exact ruleset, reporting pass probability with confidence intervals, expected attempts, and cost. License: MIT. Page: https://www.luxalgo.com/prop-firm-sim/
- [edge-stats](https://github.com/LuxAlgo/edge-stats): Trading statistics engine: asks how often a setup worked on your own market data, as one query, P(outcome | conditions), with the sample size and confidence interval on every number. License: MIT. Page: https://www.luxalgo.com/edge-stats/
- [whale-options](https://github.com/LuxAlgo/whale-options): Options-flow engine that runs on your own machine: it watches options trades as they print, flags sweeps, blocks, and split orders, and shows the math behind every score. License: MIT. Page: https://www.luxalgo.com/whale-options/
- [market-trackers](https://github.com/LuxAlgo/market-trackers): The public record of US markets as open infrastructure: congressional trades, insider filings, federal contracts, lobbying, and more, parsed from primary sources with a link to the source document on every row. License: MIT. Page: https://www.luxalgo.com/market-trackers/
- [market-trackers-data](https://github.com/LuxAlgo/market-trackers-data): Free daily dumps of the Market Trackers datasets: normalized JSON with Parquet siblings, published every day by CI from market-trackers. No API keys, no accounts. License: CC0-1.0. Page: https://www.luxalgo.com/market-trackers/
Share or continue the analysis
Share this audit
Discuss with AI
Added 9/28/2026
docs.luxalgo.com - AI readiness audit | llmsmap.me