bedrud-api

Document Bedrud REST API endpoints, middleware, status codes, and DTO definitions.

6|1|Updated May 4, 2026
One-click install
npx skills add https://github.com/themadorg/bedrud --skill bedrud-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bedrud-api
Source: https://github.com/themadorg/bedrud/tree/main/.agents/skills/bedrud-api
Command: npx skills add https://github.com/themadorg/bedrud --skill bedrud-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documents Bedrud API endpoints, middleware, request/response shapes, status codes, and DTO definitions to enable clear API discovery and validation.

Core Features & Use Cases

  • Comprehensive reference for authentication, room management, admin operations, preferences, and queueing, including DTO definitions and example payloads.
  • Enables tooling for API validation, integration testing, and client SDK generation across the Bedrud REST surface.

Quick Start

Review the API surface and DTO models to implement client SDKs and integration tests.

Frequently Asked Questions about bedrud-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document Bedrud REST API endpoints and DTO definitions for client SDK generation?

API validation for the Bedrud REST surface is achieved by applying documented DTO definitions, example payloads, and status codes to integration tests, ensuring alignment between models and actual request/response shapes.

What is the best way to reference Bedrud API middleware and authentication flows for integration?

The best way to reference Bedrud API middleware and authentication flows is by applying the comprehensive REST API surface documentation, which details request/response shapes and DTO models for accurate integration tasks.

Can I use the Bedrud API reference for admin operations and queue services?

Yes, you can use the Bedrud API reference for admin operations and queue services, as it provides comprehensive endpoint documentation, DTO definitions, and example payloads across these specific REST API service areas.

Does the Bedrud API documentation cover preferences and room management endpoints?

The Bedrud API documentation does cover preferences and room management endpoints, providing detailed reference material including request/response shapes, status codes, and DTO definitions for these specific services.

Why do I need DTO definitions aligned with Bedrud API models for automated tooling?

You need DTO definitions aligned with Bedrud API models for automated tooling to ensure accurate API validation, enable client SDK generation, and guarantee that integration tests match the actual REST API request and response shapes.