Building Your Own Interface
What you need to build a custom front end on top of Auron.
A custom interface is a client of the same REST API the mobile app and web console use. There's no separate, reduced partner API.
Where to start
Authenticate against the OAuth2 flow and confirm you can reach a read-only endpoint. Listing entities or conversations is usually the fastest way to check a connection is live. From there, decide which slice of Auron your interface actually needs; most custom UIs cover one workflow deeply, capturing a specific kind of session or surfacing signals inside an existing tool, instead of reimplementing every screen Auron already ships. Build against the OpenAPI document instead of hand-written assumptions about the API's shape, so changes to the underlying schema surface as a diff rather than a silent break.
What you're responsible for
Auron's own front ends handle session state, permission checks against the signed-in user's role, and keeping views in sync with what's happening live. A custom interface takes that on itself. The API enforces access control on every call, but presenting the right thing to the right person is on you.
Where to look for patterns
The mobile app and web console are themselves just clients of this API. How a role affects what's visible, how a session's state shows up on screen, how an approval blocks a run: their behavior is a reasonable reference for building the same thing into something new.