Developer & agent resources

AIDEN's coordination backend — boards, specs, agent runs, billing — is a real API, not just a UI. Authenticate with a token minted in the desktop app (Settings → API), then use any of the surfaces below.

OpenAPI specification

https://aidenapp.org/openapi.json

Full OpenAPI 3.1 document for the AIDEN Coordination API, generated from the live handler registry. Every operation has a unique operationId, typed bearer security, and JSON error schemas.

curl -s https://aidenapp.org/openapi.json | jq .info.title

MCP server (Streamable HTTP)

https://aidenapp.org/api/mcp

Call AIDEN's coordination API as native tools from Claude, ChatGPT, or any MCP client. Stateless JSON-RPC over HTTP; same bearer token as the REST API.

{
  "mcpServers": {
    "aiden": {
      "url": "https://aidenapp.org/api/mcp",
      "headers": { "Authorization": "Bearer <your-token>" }
    }
  }
}

API documentation

https://docs.aidenapp.org

Guides, concepts, and reference for the coordination model: orgs, projects, boards, specs, agents, billing.

llms.txt site index

https://aidenapp.org/llms.txt

The whole site in markdown, structured for LLM consumption: product facts, every article, tools, contact channels.

Sitemap

https://aidenapp.org/sitemap.xml

Every indexable URL with per-page lastModified dates.

Agent manifest

https://aidenapp.org/.well-known/agents.json

Machine-readable discovery manifest listing this site's API, MCP endpoint, and content negotiation support.

Quick start

# List your projects through the generic dispatcher
curl -X POST https://aidenapp.org/api/query \
  -H "Authorization: Bearer $AIDEN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"operation": "projects.list", "params": {}}'

Errors are always JSON: { code, message, status } — never an HTML page. Questions? Reach support@aidenapp.org.