Auron as a Headless Backend
Using Auron's API and skills without any of its front-end surfaces.
Auron's entire server-side API is described as a standard REST surface, with an OpenAPI document at /v1/openapi.json and endpoints mounted at /v1/*. It's the same API the mobile app and web console call, just reachable directly.
Authentication
Server-to-server access uses the same OAuth2 flow described in Setting Up Auron in Claude, including client-credentials grants for backends with no human in the loop. Access is scoped the same way any other client's is: only to what was explicitly granted, checked against the calling user or service's role.
What's exposed
Effectively everything covered in Configure Auron and Core Concepts: agents, conversations, entities and records, knowledge, signals, automations, as REST resources with request and response schemas defined in the OpenAPI document. See API Reference for how to browse it.
Skills as tool sources
Beyond calling the API directly, an organization can register external tool servers that its agents draw on. See Skills. That's what lets an agent reach outside Auron's own data during a session instead of being limited to it.