'endpoints' 검색 결과

Review technical claims and deliverables by checking evidence and testing alternative explanations. Confirm that references and API endpoints exist, then report verified, unverified, or contradicted claims alongside evidence and an overall review verdict.

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

• Check claims in technical documents
• Verify URLs, package names, and API endpoints
• Review another agent's deliverables

Test Android and iOS apps by capturing real app traffic and checking backend APIs. When traffic is blocked or cannot be replayed, use decompilation and runtime inspection to uncover endpoints, inspect secrets, or understand request signing.

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

• Capturing mobile app traffic and testing backend APIs
• Finding hidden API endpoints and embedded credentials
• Investigating certificate pinning that blocks traffic inspection

Inventory old and undocumented API versions, then compare their authentication, request limits, input validation, and exposed fields with current versions. Uses API specifications and archived records to identify overlooked endpoints with weaker security controls.

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

• Finding API versions left reachable after deprecation
• Comparing old and current OpenAPI or Swagger specifications
• Checking security differences between API versions

Databricks Model Serving endpoint lifecycle and ops. Use when asked to: CRUD serving endpoints (CLI or MLflow Deployments client); configure traffic routing for A/B / canary deploys and zero-downtime version swaps; retrieve OpenAPI schemas; inspect logs, metrics, or permissions; manage legacy AI Gateway rate limits (not Unity Gateway); discover Foundation Model API endpoints at runtime; integrate endpoints into Databricks Apps; or stream from off-platform clients (Vercel AI SDK v6, standalone Node.js). NOT for: Unity Gateway CRUD and management (databricks-unity-gateway), training, MLflow autologging, UC registration, custom PyFunc/ResponsesAgent authoring (databricks-ml-training); Knowledge Assistants/Supervisor Agents (databricks-agent-bricks); MLflow evaluation (databricks-mlflow-evaluation).

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

Debug 404 errors for API endpoints in microservice architectures where code exists but routing sends requests to wrong service. Use when: (1) API endpoint returns 404 despite code being deployed, (2) Multiple services share same hostname via HTTPRoute/Ingress, (3) Service logs show "Health server" but you expected API endpoints, (4) Monorepo deploys multiple images and endpoint might be in different service than expected. Covers: verifying which service handles which paths, HTTPRoute path precedence, testing endpoints directly from inside cluster, matching image tags across services.

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

API endpoint design and testing for vehicle insurance data platform. Use when designing new API endpoints, testing existing ones, validating response formats, or debugging API issues. Covers 11 core endpoints including 3 new pie chart distribution endpoints, parameter validation, error handling, and integration patterns.

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

Use when testing APIs and web frameworks for mass assignment vulnerabilities where user-controlled request body fields are bound directly to model attributes without a field allowlist. Trigger on: ORM update/create endpoints, REST APIs accepting JSON body, Rails strong parameters, Django model forms, Laravel fillable/guarded, Node.js Mongoose/Sequelize, PUT/PATCH requests, registration endpoints, profile update endpoints, GraphQL mutations. Detects privilege escalation via role/admin/isAdmin fields, plan upgrades via subscription fields, and horizontal access via ownerId/userId injection.

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

Manages Agent Platform serving endpoints. Use when you need to create, list, describe, update, or delete serving endpoints for model deployment on Agent Platform. Also use when troubleshooting endpoint permission, quota, or resource busy errors. Don't use for deploying models to endpoints or for running model evaluations.

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

Pure API reference for reddapi.dev - authentication, all endpoints (vector search, semantic search, trends, subreddit lookup), request parameters, response schemas, and error codes, with no research-workflow framing. Use when the user wants raw endpoint documentation, is debugging a reddapi.dev integration, needs exact request/response field names, or asks for 'reddapi API reference', 'reddapi.dev endpoints', or 'reddapi error codes'. For guided research workflows and query playbooks, see reddit-research. For B2B lead scoring, see reddit-leads.

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

Generates CRUD REST API endpoints with request validation, TypeScript types, consistent response formats, error handling, and documentation. Includes route handlers, validation schemas (Zod/Joi), typed responses, and usage examples. Use when building "REST API", "CRUD endpoints", "API routes", or "backend endpoints".

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

API와 모듈 사이의 입출력을 정의하고 이름, 오류 형식, 입력 검증을 통일합니다. 기존 호출 측과의 호환성과 재시도로 인한 중복 처리도 고려합니다.

• 새 REST API를 설계합니다
• 화면과 서버 사이의 데이터 규격을 정합니다
• 호환성을 유지하며 API를 확장합니다

Generate images and videos using AI models on fal.ai. The skill covers Flux, SDXL, ideogram, and other community-hosted model endpoints, providing an entry point for requesting generation through an agent.

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

• Requesting image generation through fal.ai
• Requesting video generation through fal.ai
• Specifying Flux, SDXL, or ideogram for image generation

Manage OmniRoute API keys by creating, listing, rotating, and revoking them. Set access permissions, allowed models, spending limits, and expiration dates for each key to control access to proxy and management endpoints.

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

• Create API keys with limited permissions
• Rotate or revoke existing keys
• Set spending limits and expiration dates

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

Generate API documentation from TypeScript and JavaScript source code. Extract JSDoc comments, fill gaps in public API descriptions, and produce OpenAPI 3.0 definitions, a standard format for describing HTTP endpoints.

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

• Document public functions, classes, and interfaces
• Fill gaps in JSDoc comments
• Generate OpenAPI 3.0 definitions for HTTP endpoints

Review HTML forms and JavaScript requests to find data sent over unencrypted HTTP. Check submission URLs, pages with implicit form destinations, and server redirects, then update endpoints to use HTTPS.

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

• Checking login form submission URLs
• Reviewing fetch() and XMLHttpRequest endpoints
• Checking forms without an action attribute

Build REST API endpoints, the routes applications use to exchange data, with input validation, authentication, access checks, error handling, and documentation. Covers creating, reading, updating, and deleting records, plus pagination and consistent response formats.

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

• Adding a user registration API
• Building routes to create, read, update, and delete records
• Adding pagination and filters to list APIs

Design APIs and interfaces between parts of an application with clear input and output types, consistent errors, and predictable names. The guidance helps you extend existing interfaces while preserving compatibility for the code that uses them.

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

• Designing new REST or GraphQL endpoints
• Defining contracts between frontend and backend
• Reviewing changes to a public interface

Trace server-side request forgery, where a server fetches a supplied URL, through internal services and metadata endpoints in a CTF sandbox. Document credential scope and distinguish successful token extraction from access actually accepted by another service.

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

• Tracing server-side requests to internal services
• Checking metadata access and token scope
• Distinguishing token extraction from accepted access

Set up Python APIs with FastAPI using organized project templates. Build routes, asynchronous database operations, authentication, and error handling, with examples for sharing dependencies and testing endpoints through a separate test database.

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

• Set up a new FastAPI project
• Build a Python API with asynchronous database access
• Organize authentication and shared dependencies

Compare C# Web API source code with its TypeScript or JavaScript clients to find mismatched data fields, required inputs, and response handling. Receive an audit report showing client impact, severity, and confidence in each match.

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

• Check client impact before merging a DTO or controller change
• Audit API compatibility before a release
• Find stale request fields and missing response fields

Use CloudFox to inspect AWS and Azure resources through read-only queries. Identify exposed endpoints, secrets, permissions, and role trust relationships, then organize findings into files for reviewing configuration weaknesses and potential paths to broader access.

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

• Inventorying an unfamiliar AWS or Azure account
• Finding internet-facing resources
• Mapping role trust relationships and permissions

Turn API code into documentation covering endpoints, inputs, authentication, responses, and errors. Add request examples in multiple languages and usage guides to help developers understand and start using the API.

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

• Writing documentation for a new API
• Updating API documentation after code changes
• Preparing API guides for new developers or external users

Explore local or remote repositories with Repomix CLI to understand their structure, locate related code across files, and review file counts and estimated tokens, the units AI models use to process text.

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

• Understanding an unfamiliar project's structure
• Locating authentication code and API endpoints
• Checking file counts and estimated AI tokens