Extension SDK overview

Problems they solve

Built-ins cover most generic cases. Your private ERP formats, bespoke documents, IM channels, and internal APIs won’t ship by default—SDKs cover that gap.

Each SDK maps to one extension surface:

SDK	You extend	Typical examples
parser-sdk	“How we read & chunk files”	Custom G-code, ChemDraw patents, private IDL
tool-sdk	“One more callable capability for the AI”	Internal ERP stock checks, BOM APIs
source-sdk	“Where data originates”	Pull from Feishu space, SharePoint, Notion, SVN into KB
channel-sdk	“Where the AI shows up in chat”	DingTalk, Slack, custom IM, ticketing UIs

All four share plugin-sdk-core—manifest schema, CLI scaffolding, tenant isolation, audit logging—learn once, reuse everywhere.

How to obtain packages

SDKs are not on public PyPI

Extension SDKs are customer-private packages. Email:

info@nox-lumen.com

Include:

Company / team name
Which surface (parser / tool / source / channel)
Rough use case

We respond with install steps + credentials + quick-start templates.

Pick the right SDK

Rendering diagram…

Shared dev flow

Same cadence for every SDK:

# 1) Install (after receiving the private package)
pip install ragbase-parser-sdk      # or tool-sdk / source-sdk / channel-sdk
 
# 2) Scaffold
ragbase-cli init parser my-parser   # parser / tool / source / channel
cd my-parser
 
# 3) Implement (see each SDK page)
vi src/my_parser/main.py
 
# 4) Local dry-run (each SDK ships a runner)
ragbase-cli parse-test --input sample.docx
 
# 5) Validate + build
ragbase-cli skill validate
ragbase-cli skill build
 
# 6) Push to marketplace / private tenant
ragbase-cli skill push

Per-SDK nuances live on their dedicated pages.

When enterprises actually ship SDK work

Industry	Most likely SDK
Automotive R&D	parser-sdk (ARXML subsets, tool outputs); source-sdk (continuous DOORS Next sync)
Smart manufacturing	parser-sdk (CAD / G-code); tool-sdk (MES / ERP); channel-sdk (line-side ticketing)
Office automation	source-sdk (internal doc systems); channel-sdk (custom IM)