'openapi' 검색 결과

Wire a PostHog endpoint into a client app or SDK. Covers fetching the OpenAPI spec, generating a typed client with openapi-generator or @hey-api/openapi-ts, sending the right auth header, shaping the variables payload (HogQL code_name vs insight breakdown property), handling rate-limit and materialised-endpoint error responses. Use when the user says "how do I call my endpoint", "generate a client for this", or "what auth header do I use".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Provides patterns to generate comprehensive REST API documentation using SpringDoc OpenAPI 3.0 and Swagger UI in Spring Boot 3.x applications. Use when setting up API documentation, configuring Swagger UI, adding OpenAPI annotations, implementing security documentation, or enhancing REST endpoints with examples and schemas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates OpenAPI 3.0/3.1 specs, TypeScript client types, and curl examples from existing route handler code. Supports Express, Next.js API routes, Fastify, and Hono. Produces complete documentation including auth requirements, rate limits, error codes, and request/response examples. Activate on: 'generate API docs', 'OpenAPI from code', 'document endpoints', 'API reference', 'swagger generation', 'endpoint documentation'. NOT for: API design from scratch (use api-architect), deployment (use devops-automator), testing (use test-automation-expert).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates OpenAPI docs. MS.AspNetCore.OpenApi (.NET 9+), Swashbuckle migration, NSwag.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Find available AI models across configured providers and browse a catalog that includes provider-specific variants. Inspect individual models and create or update aliases, alternative names used to refer to models.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• List models available across configured providers
• Browse provider-specific model variants
• Create or update a model alias

Configure HTTP, HTTPS, and SOCKS proxies for requests to external providers. Manage shared or provider-specific rules, test connections, and control proxy rotation to define which intermediary servers handle outgoing requests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Set shared proxy rules for outgoing requests
• Configure a different proxy for each provider
• Test proxy connectivity

Register and manage webhook endpoints, which receive event notifications from OmniRoute. Choose events such as completed requests or exceeded quotas, test delivery, inspect delivery history, and manage retries when notifications need another attempt.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Set up notifications for completed or failed requests
• Configure quota exceeded notifications
• Validate and test notification destinations

Manage how context, the text supplied to an AI, is compressed with RTK filters. Preview compression on real prompts, validate and install filter files, and inspect filter loading diagnostics.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preview compression on real prompts
• Validate and install RTK filter files
• Inspect filter loading diagnostics

Handle system backups and restore data from backup files while managing a SQLite database. The skill also covers data export, import, and incremental snapshots, which capture changes since an earlier saved state.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a system backup
• Restore data from a backup file
• Export or import SQLite data

Set spending limits, token quotas, and rate limits, which restrict requests over time. Review current consumption and apply controls per API key or globally to manage AI costs across providers.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Set spending limits for AI usage
• Assign token quotas per API key
• Review and update global rate limits

Manage embedded services such as 9Router and CLIProxyAPI through local service APIs. Install, start, stop, restart, or update services, then check their status, retrieve logs, and configure automatic startup.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Installing and starting embedded services
• Stopping or restarting services
• Checking service status and logs

Synchronize OmniRoute configuration, provider connections, and settings with cloud storage. Manage authentication for the cloud worker, a remote service, along with its credentials and remote backup destinations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Synchronize OmniRoute settings with cloud storage
• Initialize cloud synchronization
• Update cloud worker credentials

Manage cached LLM responses, which are saved answers available for reuse. Inspect statistics and stored entries, clear cached data, and configure expiration policies and similarity thresholds that govern when answers can be reused.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Inspecting response cache statistics
• Clearing saved responses
• Adjusting cache expiration policies

Design and review API contract tests, which check agreed request and response behavior. Examine schemas, server output, and client parsing to identify compatibility problems, reproduce failures locally, and report gaps in test coverage.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking client impact before changing an API response
• Investigating client and server disagreements at runtime
• Reproducing compatibility failures with local test data

Choose between REST, GraphQL, and tRPC based on who uses an API and how it is deployed. Define consistent responses, pagination, authentication, and versioning, supported by concrete request examples and failure cases.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choose an API style for known clients
• Standardize response and error formats
• Design pagination for changing data

Publish new text, image, article, or video posts to Binance Square using local scripts. Keep supplied text unchanged while the scripts upload media, generate video covers, and handle publication.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Publishing a short text post to Binance Square
• Sharing charts with up to four images
• Publishing a long article with a cover

Design and review REST and GraphQL APIs with consistent naming, data structures, error responses, pagination for large result sets, and versioning strategies. Helps teams define shared standards and plan changes that existing clients can adopt gradually.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing a new REST or GraphQL API
• Reviewing API specifications before implementation
• Establishing shared API design standards

Choose how an API, the interface software uses to exchange data, should work. Covers REST, GraphQL, and tRPC selection, consistent responses, pagination, versioning, authentication, request limits, documentation, and security review considerations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing between REST, GraphQL, and tRPC
• Standardizing API responses, errors, and pagination
• Planning authentication, request limits, and versioning

Find and retrieve official OpenAI documentation to answer API integration questions with source evidence. Check endpoint definitions, parameters, and documented limits, and receive setup guidance when the documentation connection is unavailable.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Verify specifications before integrating an OpenAI API
• Check endpoint parameters and schemas
• Support technical explanations with official documentation

Turn 飞书 API operations into reusable skills for AI agents using lark-cli. Create SKILL.md instructions for individual commands or multistep workflows, documenting required permissions, data passed between steps, and failure recovery.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Package a 飞书 API operation as a reusable skill
• Document a workflow involving several API calls
• Identify API parameters and required permissions

View and edit whiteboards embedded in 飞书 cloud documents. Export previews, SVG vector images, diagram source code, or structural data, and update boards using Mermaid, PlantUML, SVG, or the native OpenAPI format.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Exporting whiteboards as images
• Retrieving diagram source code
• Updating boards from Mermaid or PlantUML code

Turn a website's observable HTTP traffic into a best-effort OpenAPI 3.1 spec by analyzing a `browser-trace` capture. Use when the user wants to discover/extract API endpoints from a browser session, build an OpenAPI doc from network traffic, or document a third-party site's XHR/fetch surface for client integration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Golang OpenAPI/Swagger documentation with swaggo/swag — annotation comments (@Summary, @Param, @Success, @Router, @Security), swag init code generation, framework integrations (gin, echo, fiber, chi, net/http), security definitions (Bearer/JWT, OAuth2, API key), and struct tags (swaggertype, enums, example, swaggerignore). Apply when adding or maintaining Swagger/OpenAPI docs in a Go project, or when the codebase imports github.com/swaggo/swag, github.com/swaggo/gin-swagger, github.com/swaggo/echo-swagger, github.com/swaggo/http-swagger, or github.com/swaggo/files.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.