Keep HTTP outside the business code

Apply the declarative linking boundary to existing functions, layered Python services, and reusable libraries.

Guides#

Start from one function ### Expose a Python function as an HTTP API without decorators Map an unchanged typed function to a route, validate the manifest, and call it through local preview. Separate domain and transport ### Keep Python business logic independent from FastAPI Decide when route decorators belong in the application and when HTTP should remain an external adapter. Start from a package ### Turn a Python library into an API with YAML Link functions in a multi-module package while preserving normal absolute, relative, and lazy imports.

Need the exact contract?#

The guides explain architectural choices. Use the reference when you need field-level rules or complete command options.

• Linking YAML reference
• Validate and preview CLI reference
• Runnable example catalogue

Build and diagnose with clear context#

Build with an AI assistant takes you from a tested function to a validated manifest and a local HTTP request. Trace a route back to Python follows an HTTP log through the manifest into a multi-module project.

Choose the right framework#

Compare Linking and Flask for explicit handlers and extension points, or Linking and FastAPI for rich request and response models. The FAQ covers installation and independence from APIZIT hosting.