From schema to agent-callable API in four steps
UnitAPI is designed for teams that want reusable backend flows without losing the clarity of typed contracts, serverless deployment, and tenant-aware auth.
Core flow
1. Model the capability in a schema
Define entities, tenant boundaries, and workflow rules so the service starts from a clear contract instead of ad-hoc endpoints.
2. Generate the API surface
UnitAPI turns that schema into typed routes, catalog metadata, and an API footprint that can be discovered by apps and agents.
3. Issue tenant access
Hand the right tenant an API key or console-backed auth path so every call stays scoped to the workspace that owns the data.
4. Let apps and agents call the service
Use the OpenAPI description, generated client, or your own tool wrapper to automate business flows without bypassing the API.
Architecture summary
- • Static marketing and console surfaces can stay fast while the APIs run as serverless backend services.
- • Catalog entries advertise auth mode, pricing tier, and OpenAPI discovery so tooling can reason about what is callable.
- • Tenant isolation sits at the center of the platform: each generated service is expected to keep requests scoped to the current partner.
Security and isolation notes
- • Use scoped API keys or authenticated console sessions rather than direct database credentials.
- • Prefer tenant-scoped automation so agents can only act inside the workspace they were issued for.
- • Cross-origin flows must be explicit, including credential handling and CORS allow-lists for public forms and console auth.