RADZOR
ComponentsRecipesDocsContributeGitHub
Get Started
RADZOR

The universal component registry for LLM-driven development. Empowering developers to build better apps, faster.

Product
  • Components
  • Standard
Resources
  • Documentation
  • API Reference
  • AI Agent Integration
  • Pipeline Guide
  • MCP Server
Community
  • GitHub
  • X / Twitter
  • Discord

© 2026 Radzor Registry. All rights reserved.

npx radzor@latest add <component>

Add components.
Let your LLM wire them.

Radzor is a component registry with machine-readable manifests. Copy source code into your project with one command — your AI reads the manifest and integrates it for you.

Browse ComponentsHow it works
Missing a component? Request it
terminal
$ npx radzor@latest add audio-capture

✓ @radzor/audio-capture@0.1.0
  components/radzor/audio-capture/src/index.ts
  components/radzor/audio-capture/radzor.manifest.json

✓ Done! 2 files added.
radzor.manifest.json
{
  "name": "@radzor/audio-capture",
  "inputs": [{ "name": "sampleRate" }],
  "actions": [{ "name": "startRecording" }],
  "events": [{ "name": "onSpeechStart" }]
}

How it works

Three steps. No config, no lock-in, no black-box packages.

1. Add with CLI

npx radzor@latest add audio-capture copies the source code directly into your project. Like shadcn/ui — the code is yours.

2. Manifest included

Each component ships with a radzor.manifest.json describing its inputs, outputs, actions, and events.

3. LLM integrates

Your AI reads the manifest and generates the integration code. No documentation hunting, no guessing APIs.

Available Components

Standardized building blocks ready for LLM-driven development.

Browse Registry
Audio & Voice

Audio Capture

Browser-based audio recording with configurable sample rate, format, and real-time streaming.

4 in2 out4 actions3 events
2 connections
Authentication

OAuth Authentication

Multi-provider OAuth 2.0 authentication with session management and token refresh.

4 in3 out3 actions3 events
3 connections
Payment

Stripe Checkout

Complete Stripe payment integration with subscriptions, webhooks, and refund handling.

3 in3 out4 actions3 events
2 connections
Chat & Messaging

Realtime Chat

WebSocket-based real-time messaging with rooms, typing indicators, and message history.

3 in2 out4 actions5 events
2 connections
AI & ML

LLM Completion

Multi-provider LLM text generation with streaming, multi-turn conversations, and tool calling.

6 in3 out2 actions3 events
5 connections
Messaging

Email Send

Transactional email delivery via SMTP or API providers with templates and attachments.

6 in2 out2 actions2 events
5 connections
Storage

File Upload

Local and S3-compatible file uploads with validation, presigned URLs, and metadata tracking.

4 in3 out3 actions3 events
2 connections
Networking

Rate Limiter

Token bucket and sliding window rate limiting with configurable quotas and automatic cleanup.

4 in2 out3 actions2 events
2 connections
View All Components
Composability

Components that wire together

Each component declares typed inputs and outputs. Your LLM reads the manifest and automatically chains them into complete features.

Voice Assistant

Capture voice → transcribe → generate response → speak it back

Speech to Text

→ transcription

LLM Completion

→ response

Text to Speech

→ audioStream

RAG Pipeline

Scrape content → store embeddings → query with LLM

Web Scraper

→ scrapedData

Embeddings Store

→ searchResults

LLM Completion

→ response

Payment Flow

Create checkout → receive webhook → send confirmation

Stripe Checkout

→ sessionUrl

Webhook Receiver

→ eventPayload

Email Send

→ messageId

Powered by composability in each manifest

Why a manifest?

Documentation is for humans. Manifests are for LLMs. A radzor.manifest.json describes everything an AI needs to integrate a component — inputs, outputs, actions, events, and composability rules.

  • Your LLM reads the manifest, not hundreds of doc pages
  • Typed inputs/outputs prevent hallucinated API calls
  • Composability rules let AI wire components together
  • Open source — no vendor lock-in, no runtime dependency
Read the Spec

The workflow

// 1. Add the component
$ npx radzor@latest add stripe-checkout
// 2. Tell your LLM to use it
"Use the radzor.manifest.json in
components/radzor/stripe-checkout/
to add payments to my app"
// 3. LLM generates the integration
import { StripeCheckout } from "./components/radzor/..."
const checkout = new StripeCheckout({ ... })
Community

Missing a component?
Ask for it.

Tell us which component costs you the most time, and we'll build it — with a full manifest, LLM docs, and production-ready code.

→A Stripe checkout component with webhook handling
→An S3 file uploader with progress events
→A rate-limiter with sliding window algorithm
→An email queue with retry and backoff

Drop your request on Discord

Join the community, post in #components-requests, and describe what you need. We prioritize based on real demand.

Request on Discord

Start building with Radzor

Browse the registry, add a component, and let your LLM handle the integration. Or build your own and share it with the community.

$ npx radzor@latest add audio-capture
Browse ComponentsCreate a Component