FastAPI Router01 / information

Give every request a clear route.

Turn a named resource into a FastAPI CRUD router with typed responses, pagination bounds and authentication dependency hooks.

GET/api/projects200
GET/api/projects/{id}200
POST/api/projects201
PATCH/api/projects/{id}200
DELETE/api/projects/{id}204

Five handlers from one original Microsoft template. The paths above are the Project resource used in our actual local verification.

You provide

Your application's contracts.

Resource names, Pydantic request and response models, a User model, authentication functions and an async service layer.

You receive

A router you can integrate.

List, get, create, patch and delete handlers; explicit 201 and 204 responses; 404 handling; and bounded list parameters.

Authentication is only the first gate.

The original PATCH ownership check is commented out, and DELETE has no ownership check. Our local run confirmed that a different authenticated user can update and delete a record. Add application authorization before working with protected resources.

Inside the original package

Small enough to understand.

SKILL.mdQuick start, authentication patterns, integration steps and Python resource-lifetime guidance.
assets/template.pyThe five-handler router, with three resource-name placeholders.
references/capabilities.mdA checklist for validation, dependencies and production integration.

The Microsoft MIT license, a provenance note and an original promotional cover accompany the unchanged source. Generated applications and test dependencies stay outside the package.

A good fit

Python developers adding a resource to an existing FastAPI application, or teams seeking a compact route pattern to review and adapt.

Choose another tool for

A complete backend, JWT implementation, database, persistence, tenant isolation, automatic deployment or production security certification.

Use it with your coding assistant.

Open the Skill with an assistant that can read local Markdown and edit Python files. Copy the template, substitute the resource names and supply the documented application imports.

Runtime work needs Python, FastAPI and Pydantic. No Azure account or vendor API key is required for the local route workflow. Assistant model access and any database or hosting may have separate costs.

32 local behavior assertions passed, including a fresh-ZIP repeat. This is one synthetic Project fixture executed by Codex, with no speed, model-accuracy or production-readiness claim. Upstream is active but explicitly Work in Progress.