LiteSOC Is Now LLM-Friendly

If you use Cursor, Claude, GitHub Copilot, or any AI-assisted editor to write code, today's update is for you.

LiteSOC now ships a complete LLM context layer — a set of routes that expose every page of the platform as clean, crawlable Markdown. One URL gives your AI editor the full picture of our API, events, plans, and integrations so it can generate a working integration without you writing a single prompt.

The Problem With AI + Documentation

When you ask an AI editor to "add LiteSOC security tracking to my login route", it usually does one of three things:

1. Hallucinates an API that doesn't exist
2. Uses a months-old snapshot of our docs from its training data
3. Asks you to paste in the relevant docs manually

None of these are good. The root cause is that most documentation sites render their content inside JavaScript-heavy SPAs that AI agents can't read. The raw text is buried inside React component state, tab panels, and dynamic query results.

We've fixed that.

What We Built

/llms.txt — The Index

Following the llmstxt.org proposal, https://litesoc.io/llms.txt is a plain-text file that gives AI agents a structured map of everything on the site:

# LiteSOC

> LiteSOC is a lightweight Security Observability SaaS for startups...

## Documentation

- [API Reference](https://litesoc.io/docs/api.md): Complete API reference — 26 standard events...
- [Integrations](https://litesoc.io/docs/integrations.md): Supabase, Auth0, n8n...
...

## SDKs

- [Node.js](https://github.com/LiteSOC/litesoc-node)
- [Python](https://github.com/LiteSOC/litesoc-python)
- [PHP](https://github.com/LiteSOC/litesoc-php)

This is the entry point. Every page has a corresponding .md URL.

10 Markdown Routes

Page	Markdown URL
Pricing	https://litesoc.io/pricing.md
Features	https://litesoc.io/features.md
API Reference	https://litesoc.io/docs/api.md
Integrations	https://litesoc.io/docs/integrations.md
How It Works	https://litesoc.io/how-it-works.md
Security & Compliance	https://litesoc.io/security.md
Help Center	https://litesoc.io/help.md
Docs Overview	https://litesoc.io/docs.md
Changelog	https://litesoc.io/changelog.md
About	https://litesoc.io/about.md

Every route returns Content-Type: text/markdown and is pre-rendered at build time (force-static) — zero latency, CDN-cached, always in sync with the UI because they share the same data modules.

/llms-full.txt — Everything in One Shot

For agents that want the complete context in a single request, https://litesoc.io/llms-full.txt returns one giant Markdown document containing:

• All product pages (About, Features, Pricing, Security, Changelog, How It Works)
• The full API reference with all 26 standard events, endpoints, rate limits, and response headers
• Every help center article — including the complete body text of all 17 articles across 7 categories
• All published blog posts, fetched live from the database

The document is rebuilt at most once per hour via ISR and served stale-while-revalidating at the CDN edge, so it's fast without ever going stale for long.

How to Use It

Cursor

Add this to your cursor rules, or just type it in the composer:

@https://litesoc.io/llms.txt

Cursor will fetch the index and automatically pull the relevant .md pages based on your question. Ask it to add a login tracker to your Express app and it'll read docs/api.md, understand the auth.login_success and auth.login_failed events, and write the correct code.

Claude

Paste the URL into any Claude conversation:

@https://litesoc.io/llms.txt

Add LiteSOC security tracking to my Next.js app. I use Supabase Auth.

Claude will fetch the index, discover the integrations page, and generate a complete implementation including the Supabase webhook handler.

For Full Context (Claude Projects, Cursor Rules)

Use llms-full.txt when you want to load everything upfront — ideal for a Claude Project or a persistent Cursor rules file:

@https://litesoc.io/llms-full.txt

It's Always In Sync

The Markdown routes don't have a separate content pipeline to maintain. They're powered by the exact same data modules that render the UI:

• lib/pricing-data.ts → used by /pricing (UI) and /pricing.md (LLM)
• lib/features-data.ts → used by /features (UI) and /features.md (LLM)
• lib/changelog-data.ts → used by /changelog (UI) and /changelog.md (LLM)

When we update pricing or add a new event type, the Markdown routes update automatically at the next build. No docs lag.

Try It Now

Paste this into your AI editor of choice:

@https://litesoc.io/llms.txt

Then ask it to add security event tracking to your app. Let us know how it goes — we're @mylitesoc on X.