How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Plandex Plans API

Long-running, branchable units of AI coding work over loaded context.

Plandex Plans API is one of 15 APIs that Plandex publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 9 JSON Schema definitions.

Tagged areas include Plans. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and 9 JSON Schemas.

This API exposes 12 operations across 10 paths. It is described by OpenAPI 3.2.0, at version 2.

Requests are made against 2 base URLs: http://localhost:8099, https://api.plandex.ai.

12 operations 10 paths 0 schemas 2 DELETE6 GET3 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2
Base URL
http://localhost:8099
Authentication
HTTP Bearer
Contact
License
Terms of Service
Resource Areas
1

Authentication & Security 1

Plandex Plans API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — Bearer token issued by the Plandex server on sign-in. Used by the CLI/REPL for all authenticated API calls.

Paths & Operations 12

Across 10 paths, the API surfaces 12 operations — 2 DELETE, 6 GET, 3 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Plans 12

Long-running, branchable units of AI coding work over loaded context.

POST
/projects/{projectId}/plans
Create Plan
createPlan 1 param → 201
DELETE
/projects/{projectId}/plans
Delete All Plans In Project
deleteAllPlans 1 param → 204
GET
/plans
List Plans
listPlans → 200
GET
/plans/archive
List Archived Plans
listArchivedPlans → 200
GET
/plans/ps
List Running Plans
listPlansRunning → 200
GET
/plans/{planId}
Get Plan
getPlan 1 param → 200
DELETE
/plans/{planId}
Delete Plan
deletePlan 1 param → 204
GET
/plans/{planId}/current_plan/{sha}
Get Current Plan At Sha
getCurrentPlanAtSha 2 params → 200
GET
/plans/{planId}/{branch}/current_plan
Get Current Plan On Branch
getCurrentPlanOnBranch 2 params → 200
PATCH
/plans/{planId}/archive
Archive Plan
archivePlan 1 param → 200
PATCH
/plans/{planId}/unarchive
Unarchive Plan
unarchivePlan 1 param → 200
PATCH
/plans/{planId}/rename
Rename Plan
renamePlan 1 param → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

plandex-plans-api-openapi.yml Raw ↑

Other APIs Plandex publishes across the network.

Plandex Accounts API
Plandex Branches API
Plandex Context API
Plandex Conversation API
Plandex Diffs API
Plandex Execution API
Plandex FileMap API
Plandex Health API
Plandex Invites API
Plandex Models API
Plandex Orgs API
Plandex Projects API
Where this information came from

This is an independent, third-party profile of Plandex Plans API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.