APIs and Developer Reference

DevJock exposes three separate APIs. Each covers a different layer of the platform, and each has its own live interactive reference you can open from the app's user menu. Pick the API that matches the layer you are working in.

The three APIs

• Task API (PHP). The interface to the brain, the issue tracker. Use it to read and write tasks and the parent-child task tree, and to work with projects, sprints, epics, workspaces, memories, and file attachments. Reach for this when your integration is about tracking or organizing work.
• AI/Agents API (Python). MCP-over-HTTP with OAuth bearer authentication. Use it to drive agents and chat: run agents, manage prompts and skills, and work with chat sessions. This is the surface for building on the agentic framework and for tools that speak MCP.
• App API. The Vercel front-end's own API, backing the web application. Use it for the operations the app UI itself performs, such as account and organization-level actions.

When to use which

Match the API to the layer, not the task at hand:

• Managing work items and their structure: Task API.
• Running agents, prompts, or chat: AI/Agents API.
• Front-end and account or organization operations: App API.

Some workflows touch more than one. Creating a task and then having an agent act on it, for example, uses the Task API and the AI/Agents API in sequence.

Live interactive references

Each API ships its own interactive reference. Open the app, then use the user menu to reach the reference for the API you need. The reference is the source of truth for endpoints, fields, and parameters, so consult it rather than relying on copied examples.