Obsidian AI Pricing: Separate Plugins, Models, and Sync

Obsidian AI pricing depends on the plugin and model access you choose, along with any optional Obsidian services. Check those components separately: a payment for the note app’s services does not by itself establish what a third-party AI plugin includes.

The practical question is what you need to buy, who charges you, and what happens when you change assistants. Tools like fenbs keep shared project decisions and progress outside the chosen AI app, so the work record can remain available while you reconsider the assistant serving it.

What are the separate parts of the bill?

Begin with the official Obsidian pricing page↗ (opens in a new tab). It separates the app from optional services such as Sync and Publish. Then identify the developer of the AI plugin you want and the model service it uses. Those are separate product decisions, even when the experience appears inside one note window.

Do not add every category automatically. Some setups bundle several parts; others need only a subset. Write “not needed” where appropriate. The goal is a complete picture of your chosen workflow, rather than an intimidating list of every possible expense.

Does the plugin include the model you want?

Find the answer for the exact plugin, rather than searching for a universal Obsidian AI subscription. Ask whether the license includes model access, lets you connect a provider you already use, or supports running a model locally. These routes can have different billing, setup, and data handling arrangements.

For a concrete example, Copilot for Obsidian’s settings documentation↗ (opens in a new tab) describes a bring-your-own-key route that connects to a model provider, with that provider handling cloud billing. This shows why plugin access and model access belong on separate lines of your worksheet. It is an example of one plugin’s arrangement, not a rule for every plugin.

An API key is a credential an application uses to call a service. If a plugin asks for one, check which provider receives the requests and how that provider bills the account. Do not assume a subscription you use for an assistant’s website also covers requests from an unrelated plugin. Verify the entitlement before connecting it.

For choosing the extension itself, use the separate Obsidian AI plugin guide. Once you have a candidate, focus this comparison on the specific features you will use and the accounts those features require.

Which usage can change your total?

Check whether each component is billed by subscription, measured usage, or a combination. Where a provider measures usage, its current billing documentation should explain the units and included allowance. You do not need to predict a whole year accurately; you need to understand which everyday actions can change the bill.

Say you are comparing help with a selected note against questions spanning a larger research collection. Run both tasks during a small trial. Observe what the plugin sends, which services run, and what appears in the relevant usage dashboard. Repeat a question once to see whether another request is recorded. Treat the result as evidence about your test, rather than a general promise.

• Check whether the chosen workflow sends a short selection, a whole note, or additional material.
• Ask whether building or refreshing a searchable collection invokes another service.
• Check what happens when a request fails or you ask for a new answer.
• Locate any available spending controls and confirm whether they stop usage or only notify you.
• Identify the account owner who can see the bill and respond to unexpected activity.

Compare useful completed work, not the number of answers generated. A setup that needs repeated corrections or constant troubleshooting may cost you more time even if its direct charges look attractive. A short log of representative tasks makes that tradeoff easier to judge.

Do you need Sync or Publish for this workflow?

Treat note availability and AI access as two questions. Do you need the same notes on several devices, a shared collection, or a website made from notes? Separately, which content must the chosen assistant read? Confirm the documented requirements of your plugin rather than buying a service because its name sounds connected to AI.

Include data handling in the decision. Obsidian’s plugin security guidance↗ (opens in a new tab) explains that community plugins can access files and connect to the internet, and cannot reliably be restricted to individual permissions. Review the plugin and provider before giving the setup sensitive work.

For your worksheet, write the purpose beside each optional service. If you cannot describe which step needs it, leave the choice unresolved until you can test it. The separate Obsidian AI setup guide covers configuring the workflow after you have chosen its parts.

How do you compare a simpler alternative?

Start with the task you actually need. Occasional help rewriting selected text may justify a different setup from continuous questions about a note collection. Shared project continuity is another need again: retaining who approved a choice and what remains unfinished is different from generating text in a note.

Use the idea of an AI brain to separate stored knowledge from the assistant that reads it. Then compare your options using the same representative tasks. Include the time required to reconnect sources, review an answer, and explain the project in a fresh session.

If an editor is also part of your work, what Cursor AI is provides a separate introduction; an editor subscription is not automatically a replacement for your note workflow. The AI memory tools hub covers other storage and continuity choices without assuming one tool should do every job.

What should you check before subscribing?

Make a short purchase record: the feature you need, the company billing it, what is included, and where you verified the terms. Check the billing period, renewal settings, and what happens when access ends. Save links to the current pages so you can revisit them without trusting an old screenshot.

Keep the first trial small enough to reverse. Use non-sensitive notes, confirm a useful result, and locate any stored output you want to preserve. Before switching providers, check both the content you keep and the connection you need to remove. A readable note does not tell you whether an old service still has access.

For a work pilot, choose one repeatable activity from how to use AI at work and record the result. In fenbs, AI context keeps the agreed approach and Where we left off available to the next connected assistant, rather than making the trial depend on one conversation.

How to do this with fenbs

1. Create a free account and add a project for the work you want to keep continuous. fenbs is free for one person, no credit card.
2. Add a task describing the representative workflow, the plugin and model choices under review, and what you still need to verify. Keep credentials and billing details out of the task.
3. Record the approach you choose in Decisions and rules, and save useful source locations in Links and listings.
4. Connect your supported assistant from Integrations. Ask it to read the project context at the start and save progress before it stops.

fenbs does not run Obsidian plugins, import your vault, or provide model access for them. It is not the right fit if you only want AI editing inside a local note. Use it when the project’s decisions and next steps need to remain available across supported assistants, alongside the notes you maintain elsewhere.