App API (Vercel)

The App API is the interface the DevJock web application uses to talk to its own back end. It runs on the Vercel front end and serves the operations the browser UI needs to render pages, submit forms, and keep views in sync. It is one of three DevJock APIs, alongside the Task API for the issue tracker and the AI/Agents API for agents and chat.

What it exposes

Think of the App API as app-facing plumbing rather than a general-purpose integration surface. It backs the screens you already see in the product: navigating Home, Chats, Projects, and Memories, working in the Developer area for Agents, Prompts, Mappings, MCP Servers, and Embed, and managing your Account and Organizations.

In practice this covers session and account state, loading and saving the data behind each view, and the glue operations the interface needs. If you are building an automation or an external integration, the Task API and the AI/Agents API are usually the better starting points. The App API exists to serve the web client.

Where it is documented

The App API has its own live interactive reference inside the DevJock app. Open it from the user menu, alongside the references for the Task API and the AI/Agents API. The live reference is the source of truth for available operations, request shapes, and responses, and it stays current with the deployed front end.

We do not duplicate the endpoint list here, because the interactive reference reflects what is actually deployed. Read the operations there and try them against your own account.

Related