Skip to main content
The Architect API is pre.dev’s core planning engine, exposed as a standalone API and MCP server. Drop it into Cursor, Claude Code, Lovable, Bolt, or your own tooling — and any coding agent suddenly plans complex builds like a senior architect.
If the Coding Agent is “pre.dev builds your app,” the Architect API is “your coding agent plans like pre.dev.”

​
Lifecycle

1. Describe

Send one natural-language prompt describing what you want built. Optionally attach context IDs from previous specs, docs URLs, or uploaded files.

2. Plan

The Architect returns a structured spec: tech stack, system design, milestones, user stories, acceptance criteria, and (with Deep Spec) granular subtasks.

3. Hand off

Feed the spec to your coding agent. It now has the architectural context to build multi-file systems correctly on the first try.

Call your first spec in 5 minutes

One curl, one API key — or install the MCP server into your editor.

​
Two ways to call it

REST API

POST https://api.pre.dev/fast-spec or /deep-spec with a Bearer token. Sync or async. Perfect for CI/CD, custom tooling, or SDK-based workflows.

MCP Server

https://api.pre.dev/mcp — one-click install into Cursor, Claude Code, VS Code, or Windsurf. Your agent calls fast_spec / deep_spec as tools.

​
When to use which

​
Endpoints at a glance

  • POST /fast-spec — High-level plan in ~1 min (~5–10 credits)
  • POST /deep-spec — Granular subtasks in ~3–5 min (~10–50 credits)
  • GET /spec-status/:id — Poll async generation progress
  • GET /list-specs — List your generated specs
  • GET /find-specs — Search specs by content
  • GET /credits-balance — Check remaining credits
See the full API Reference or grab an SDK.

​
Quick example

​
Explore

​
Why your coding agent needs it

AI coding agents are powerful, but they struggle with complex, multi-file projects without proper architecture. Built-in planning modes give basic task decomposition but lack deep architectural context, miss implementation details, and don’t reason about schemas, API contracts, or system boundaries. The Architect API equips your agent with:
  • ✅ Enterprise-grade architecture — complete system designs with schemas, contracts, and component hierarchies
  • ✅ Implementation roadmaps — sequenced build plans that guide your agent through complex projects
  • ✅ Technology decisions — pre-made architectural choices for auth, state, APIs, and more
  • ✅ Full context — your agent knows exactly what to build, how, and why