VS Code, Cursor, and compatible editors
AvailableShipped
Install the editor extension and bring Spendplane sign-in, planning, and synced project capture into VS Code, Cursor, and compatible editors.
Extensions & SDKs
Use Spendplane from your editor, browser, desktop app, or SDK without rebuilding your workflow. Keep requests OpenAI-compatible while adding sign-in, routing, redaction, and budget policy in the same path.
Our editor extension, browser extension, desktop app, and `/v1` endpoint are the real integration surfaces available now. Additional environment-specific installs build on the same governed boundary.
Shipped
Install the editor extension and bring Spendplane sign-in, planning, and synced project capture into VS Code, Cursor, and compatible editors.
Browser capture
Capture ideas and browser context, sync them into Spendplane, and protect web AI sessions directly inside Chrome.
Standalone runtime
Use Spendplane Vault for desktop sign-in, local runtime controls, hardware visibility, and a dedicated workspace surface on Windows.
Universal path
Any tool that supports an OpenAI-style base URL can route through Spendplane with the same policy and budget boundary.
Compatible now
Where a dedicated extension is not shipped yet, the same route still works through endpoint overrides, proxy settings, and the shared `/v1` contract.
Rolling out
Dedicated setup guides and install surfaces for more coding environments are next, but they all use the same governed endpoint and auth model.
Real-time prompt inspection and workspace sync inside Chrome. Install in seconds for individuals or deploy centrally across managed enterprise browsers.
Inspects outbound prompts locally inside your browser session with zero cloud prompt storage and instant workspace sync.
Enterprise IT and security teams can roll out pre-configured browser protection across internal teams from one central policy.
Public browser distribution follows Chrome Web Store publishing and review for verified one-click updates.
Keep your current SDK calls and payload format. Swap the host, keep the contract.
Keep the same workspace, policy, and routing boundary whether the request starts in the desktop app, an editor extension, or a browser session.
Enforce cost and data rules at the perimeter so enforcement is consistent across teams, tools, and extension surfaces.
Node.js / TypeScript
npm install openai
import OpenAI from "openai"
const client = new OpenAI({
apiKey: process.env.SPENDPLANE_KEY,
baseURL: "https://api.spendplane.com/v1/openai",
})
const res = await client.chat.completions.create({
model: "gpt-4.1-mini",
messages: [{ role: "user", content: prompt }],
})Python
pip install openai
from openai import OpenAI
client = OpenAI(
api_key=os.environ["SPENDPLANE_KEY"],
base_url="https://api.spendplane.com/v1/openai",
)
response = client.chat.completions.create(
model="gpt-4.1-mini",
messages=[{"role": "user", "content": prompt}],
)Use the editor extension, browser extension, desktop app, or base URL override that matches how the team actually works.
Reuse the same Spendplane workspace identity across extensions, desktop, and direct client traffic.
Set the OpenAI-compatible base URL or use the packaged extension surface where routing is already wired in.
Check routing, redaction, captured projects, and spend in the same control plane.