Plandex · FinOps Profile

Plandex Finops

FinOps framework definition for Plandex. Plandex itself is MIT-licensed and free; the hosted Plandex Cloud (now winding down as of 2025-10-03) charged a subscription plus pass-through-with-markup model credits in Integrated Models Mode, and a flat subscription in BYO API Key Mode. The dominant ongoing cost for users running Plandex (cloud or self-hosted) is upstream model-provider consumption (OpenAI, Anthropic, OpenRouter, Google, Azure, Bedrock, DeepSeek, Perplexity, Relace). This document maps that surface to the FinOps Foundation framework and FOCUS data spec so consuming organizations can build cost visibility, allocation, optimization, and accountability around Plandex.

Plandex Finops is the FinOps profile for Plandex on the APIs.io network, aligned with the FinOps Foundation Framework.

It defines 6 billable meters, billed in USD, on a monthly cycle, and pricing category hybrid.

The profile maps 9 FOCUS columns for cost-allocation reporting.

Tagged areas include AI Coding Agent, Developer Tools, FinOps, Cost Management, and FOCUS.

Category: Developer Tools / AI Coding Agent Pricing: Hybrid Billing: Monthly FOCUS v1.3
AI Coding AgentDeveloper ToolsFinOpsCost ManagementFOCUSLLMOpen Source

Framework Alignment

Framework
FinOps Foundation Framework
Data Spec
FOCUS v1.3

Charge Categories

UsagePurchaseTaxCreditAdjustment

FOCUS Columns

BillingCurrency
USD
ChargeCategory
Usage
InvoiceIssuerName
PlandexAI Inc.
PricingCategory
Hybrid
PricingUnit
subscription-month / credit-usd / provider-token
ProviderName
PlandexAI Inc.
PublisherName
PlandexAI Inc.
ServiceCategory
Developer Tools / AI Coding Agent
ServiceName
Plandex

Meters

subscription_month
Unit: month
Active months of Plandex Cloud subscription (BYO or Integrated).
plandex_credit_usage
Unit: credit-usd
Plandex credits spent against integrated model providers.
plandex_credit_purchase
Unit: credit-usd
Plandex credits purchased (one-off top-up or auto-recharge).
upstream_input_tokens
Unit: token
Input tokens consumed against upstream model providers when running self-hosted (or BYO) Plandex.
upstream_output_tokens
Unit: token
Output tokens generated by upstream model providers.
model_response_count
Unit: response
Count of model responses across plans (used by Cloud BYO trial cap).