api-design-patterns

A set of rules for designing REST APIs with FastAPI, a Python framework for building web services. It covers how to structure data models, validate requests, and format responses.

In plain words
What is it for?
Use it when creating FastAPI endpoints, Pydantic request or response models, validation rules, error handling, or API versions.
Why use it?
It reduces inconsistent API designs and helps catch invalid input and unclear error responses.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/rm2thaddeus/pixel_detective/api-design-patterns
Clone the repo
git clone --depth 1 https://github.com/rm2thaddeus/Pixel_Detective

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 3,930 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.03930
Opus 5 $0.00000 $0.01965
Sonnet 5 $0.00000 $0.00786
Haiku 4.5 $0.00000 $0.00393

Measured 2d ago against content hash f9366c07a72d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

api-design-patterns scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

backend/.cursor/rules/api-design-patterns.mdc · 534 lines

How it starts

The opening of the file, as written. The whole thing — 534 lines — stays where its author put it; the contents beside it link to each section on GitHub.

API Design & Data Modeling Patterns

🔌 RESTFUL API DESIGN PATTERNS (From Backend Services)

Proven patterns for building consistent, scalable REST APIs with FastAPI.

📋 PYDANTIC MODEL PATTERNS:

1. Request/Response Model Structure
# ✅ Consistent model organization pattern
from pydantic import BaseModel, Field
from typing import List, Optional, Dict, Any, Union
from datetime import datetime

# Base models for common fields
class BaseResponse(BaseModel):
    """Base response with common fields."""
    status: str = Field(..., description="Operation status")
    message: str = Field(..., description="Human-readable message")
    timestamp: datetime = Field(default_factory=datetime.utcnow)

# Request models with validation
class ProcessRequest(BaseModel):
    """Request model with comprehensive validation."""
    data_path: str = Field(..., min_length=1, description="Path to data")
    options: Optional[Dict[str, Any]] = Field(default_factory=dict)
    
    class Config:
        # Enable validation on assignment
        validate_assignment = True
        # Example values for documentation
        schema_extra = {
            "example": {
                "data_path": "/path/to/data",
                "options": {"batch_size": 32, "format": "jpeg"}
            }
        }

# Response models with detailed typing
class ProcessResponse(BaseResponse):
    """Response model with job tracking."""
    job_id: str = Field(..., description="Unique job identifier")
    result: Optional[Dict[str, Any]] = Field(None, description="Processing result")
2. Collection Management Models
# ✅ Pattern from collections router
class CreateCollectionRequest(BaseModel):
    collection_name: str = Field(..., min_length=1, max_length=128)
    vector_size: int = Field(512, gt=0, description="Vector dimensionality")
    distance: str = Field('Cosine', description="Distance metric: Cosine|Dot|Euclid")

class CollectionInfo(BaseModel):
    """Comprehensive collection information."""
    name: str
    status: str
    points_count: int
    vectors_count: int
    config: Dict[str, Any]
    sample_points: List[Dict[str, Any]]
    is_active: bool
    created_at: Optional[datetime] = None
    updated_at: Optional[datetime] = None

Read the full file on GitHub · 534 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 534 lines · 0 tokens per session scan A f9366c07a72d

Subscribe to this mod's changes

api-design-patterns is a cursor rule published in the GitHub repository rm2thaddeus/Pixel_Detective (21 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,930 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.