mainsequence-api-surfaces

Define FastAPI API surfaces by declaring explicit request and response models for each endpoint. This contract-driven approach structures application-facing APIs in a Main Sequence project, ensuring validation and clear data binding.

A widget-facing contract defines API response structures specifically for UI component integration. You need widget-facing contracts when building FastAPI routes that directly supply data to UI widgets, maintaining consistent expectations across application surfaces.

Consume APIDataNode and SimpleTable resources by reading published DataNodes within your FastAPI routes. This lets your API surfaces retrieve tabular data and bind producer resources into structured responses without owning the underlying logic.

Yes, you can bind user context to API routes by applying middleware to your FastAPI endpoints. This middleware intercepts requests to attach user context, ensuring API surfaces enforce project resource discovery and access rules.

Decide whether to own API logic or consume producer resources based on project needs. Consuming APIDataNode resources avoids duplicate logic, while owning logic allows custom validation when structuring FastAPI project resources.

Yes, designing API surfaces requires explicit request and response models for every endpoint. This contract-driven validation ensures alignment with project resource discovery and maintains consistent widget-facing contracts for UI integrations.