CoreStory Projects API

The projects API from CoreStory — 40 operation(s) for projects.

GitHub OpenAPI

Operations 50

POST /api/projects Create a new project with auto-generated PRD #
GET /api/projects Get organization projects with pagination #
POST /api/projects/create-and-generate Create a new project with auto-generated PRD and ingestion #
PATCH /api/projects/{project_id} Update project #
GET /api/projects/{project_id} Get project details #
DELETE /api/projects/{project_id} Delete a project #
POST /api/projects/{project_id}/transfer Transfer project to another organization #
GET /api/projects/{project_id}/status Lightweight polling status for ingestion and generation jobs #
GET /api/projects/{project_id}/pending-commits Get pending commits for a project #
GET /api/projects/{project_id}/health Get project health signals, code quality, and security findings #
GET /api/projects/{project_id}/tech-spec Get the project's Tech Spec (not base PRD) sections data #
GET /api/projects/{project_id}/prd/status Get the project's PRD generation status #
GET /api/projects/{project_id}/tech-spec/status Get the project's tech-spec generation status #
GET /api/projects/{project_id}/prd Get the project's PRD (not tech spec) sections data #
GET /api/projects/{project_id}/delete-impact What deleting a project would do #
DELETE /api/projects/{project_id}/delete Delete a project #
GET /api/projects/{project_id}/metrics/processing/summary Get latest ingestion/generation metrics for a project #
POST /api/projects/upload-repository Upload repository files and create project #
POST /api/projects/upload-repository-from-pre-ingestion Create project from an existing pre-ingestion upload #
POST /api/projects/{project_id}/prd/generate Generate the PRD sections (no Tech Spec sections) for the project #
POST /api/projects/{project_id}/tech-spec/generate Generate the Tech Spec sections (no base PRD sections) for the project #
POST /api/projects/{project_id}/prd/generate-all Generate all PRD and tech spec sections for the project #
GET /api/projects/{project_id}/prd/context Get the context for the project's latest PRD #
POST /api/projects/{project_id}/prd/context Set or update the context for the project's latest PRD #
GET /api/projects/{project_id}/prd/user-stories/catalog Get a catalog of user stories items for UI faceted browsing #
GET /api/projects/{project_id}/tech-spec/tech-user-stories/catalog Get a catalog of user stories items for UI faceted browsing #
POST /api/projects/{project_id}/reingestion/analyze Start pre-reingestion analysis for an existing project #
POST /api/projects/{project_id}/reingestion/analyze/upload Upload a codebase archive and start reingestion analysis #
POST /api/projects/{project_id}/reingestion/analyze/from-storage Start reingestion analysis from an already-uploaded archive #
GET /api/projects/{project_id}/reingestion/analyze/{job_id}/status Get reingestion analysis job status #
GET /api/projects/{project_id}/reingestion/analyze/{job_id}/coverage Get coverage results from reingestion analysis #
GET /api/projects/{project_id}/reingestion/analyze/{job_id}/excluded-files Get excluded file paths from reingestion analysis #
GET /api/projects/{project_id}/reingestion/analyze/{job_id}/included-files Get included file paths from reingestion analysis #
DELETE /api/projects/{project_id}/reingestion/analyze/{job_id} Delete a reingestion analysis job #
POST /api/projects/{project_id}/reingestion/trigger Trigger reingestion for an existing project #
GET /api/projects/{project_id}/ingestion-events List ingestion events for a project #
GET /api/projects/{project_id}/ingestion-events/{event_id}/doc-impact Doc-section impact (added/modified/removed) for an ingestion event #
POST /api/projects/{project_id}/clone Clone Project #
POST /api/projects/{project_id}/prd/{section_name}/generate Generate a specific PRD section #
POST /api/projects/{project_id}/tech-spec/{section_name}/generate Generate a specific Tech Spec section #
PATCH /api/projects/{project_id}/prd/{section_name} Update the specified PRD section #
GET /api/projects/{project_id}/prd/{section_name} Get the specified PRD section #
PATCH /api/projects/{project_id}/tech-spec/{section_name} Update the specified Tech Spec section #
GET /api/projects/{project_id}/tech-spec/{section_name} Get the specified Tech Spec section #
GET /api/projects/{project_id}/file-manifest Get the file manifest for a project #
GET /api/projects/{project_id}/file-content Stream file content from vector store by file path #
GET /api/projects/{project_id}/file-content/metadata Get file metadata from vector store #
GET /api/projects/{project_id}/config Get project operator config (stored overrides + effective values) #
PATCH /api/projects/{project_id}/config Update project operator config (partial merge) #
PATCH /api/projects/{project_id}/sync-mode Set project sync mode (manual or auto) #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/corestory:corestory-projects-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

corestory-projects-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Crowdbotics API Documentation Projects API
  description: '# CoreStory API Overview


    The CoreStory API provides programmatic access to structured insights derived from software source code. It is designed for engineering, architecture, and product teams who need to extract business logic, technical specifications, architectural relationships, and system-level context from complex or legacy codebases. By interfacing directly with CoreStory API, users can:


    - Generate full Product Requirements Documents (PRDs) from a codebase

    - Extract detailed Technical Specifications for modernization or migration

    - Query a codebase using natural language to surface implementation details, logic paths, dependencies, and architectural insights

    - Construct and visualize knowledge graphs of systems, components, and relationships

    - Ingest, store, and retrieve content from a vector store for AI-powered retrieval-augmented generation (RAG) workflows


    CoreStory is especially valuable in contexts where:


    - Codebases are large, unstructured, or under-documented

    - Product and engineering teams are onboarding to unfamiliar systems

    - Technical stakeholders require visibility into system design or feature coverage

    - Modernization, replatforming, or M&A due diligence is underway


    The API can be integrated into existing CI/CD pipelines, internal developer portals, architecture review boards, product planning processes, or documentation automation workflows. All endpoints support secure authentication and are designed for high-availability, asynchronous workloads. Output formats include JSON, Markdown, and PDF, with flexible formatting options for downstream consumption. For step-by-step usage instructions and workflows, refer to the CoreStory API Quick Start Guide. ## Features


    * **Document Generation**

    * Generate complete Product Requirements Documents (PRD)

    * Generate Technical Specifications

    * Generate individual document sections (executive overview, user personas, etc.)

    * Format documents in JSON or Markdown


    * **Vector Store Management**

    * Ingest and manage documents in vector store

    * Query and retrieve document content

    * Manage document embeddings


    * **Context Management**

    * Manage context for different document types

    * Set and retrieve PRD context

    * Support for future context types (technical specs, user stories, etc.)


    * **Knowledge Graph**

    * Generate knowledge graphs from codebase queries

    * Visualize relationships between code entities

    * Analyze code structure and dependencies


    * **API Endpoints**

    * `/api/documents/*` - Document generation and formatting

    * `/api/generate/*` - Document formatting utilities

    * `/api/vector-store/*` - Vector store management

    * `/api/agents/*` - AI agent operations

    * `/api/context/*` - Context management for documents

    * `/api/graph/*` - Knowledge graph generation and analysis


    Note: JWT authentication support coming soon. All endpoints currently provide detailed OpenAPI documentation. * **Observability**

    * OpenTelemetry instrumentation for distributed tracing

    * Prometheus metrics endpoint at `/metrics`

    * Comprehensive request/response tracking

    * Custom business metrics


    # CoreStory System Architecture


    This document provides a high-level overview of how the CoreStory platform ingests, analyzes, and serves structured software intelligence through its API. The system is designed to process codebases and related technical artifacts in order to generate product specifications, technical documents, and knowledge graph representations. ---


    ## Core Components


    ### 1. **Ingestion Layer**


    - Accepts Git URLs, file uploads, or local archives

    - Extracts source files, documentation, and metadata

    - Initiates chunking and embedding via the vector store pipeline


    ### 2. **Vector Store and Context Engine**


    - Stores chunked and embedded documents

    - Supports semantic search and document retrieval

    - Feeds LLMs with scoped context for generation and reasoning


    ### 3.'
  version: 1.33.0
servers:
- url: /
  description: Current server
security:
- BearerAuth: []
tags:


# --- truncated at 32 KB (159 KB total) ---
# Full source: https://artifacts.apis.io/corestory/openapi/corestory-projects-api-openapi.yml