Does MCP avoid OfficeMaker charges?

No. MCP and REST use the same document-generation backend. Free-host create is not billed. Paid and organisation hosts meter MCP calls the same way they meter the matching REST verbs.

Are ChatGPT or Claude charges included in OfficeMaker?

No. When those products author the structured JSON, the model provider bills that usage separately. OfficeMaker meters document-service work. Pay-per-document checkout and organisation prepaid credit apply to OfficeMaker usage, including the signed-in Create assistant. They are not an OpenAI or Anthropic subscription.

Where are seat fees and prepaid amounts shown?

After you sign in to the relevant workspace, or in a quote for education and corporate licences. This page does not invent those figures.

Pricing

How OfficeMaker pricing works

OfficeMaker has three public commercial paths: a free sandbox, pay-per-document checkout on the public site, and organisation prepaid credit on the internal workspace. Education and corporate licences are quoted for the organisation. This page does not list wallet balances, seat fees or pack prices, because those amounts are shown after sign-in or agreed in a quote. MCP and REST reach the same document-generation backend and the same metering rules.

What is free?

The public sandbox at free.officemaker.ai exposes REST under /gpt/v1/, MCP, and the ChatGPT App MCP path. It does not require an API key. Schema-led create is not billed. Preview belongs to the create response or the file you just created. OpenAPI for that host is published at free.officemaker.ai/gpt/openapi.json.

The free surface is intentionally narrow: create, preview-oriented flows, schema discovery and gap analysis for native Word, Excel and PowerPoint files. It does not include merge, edit, macros, document conversion, Excel query and update of an existing workbook, organisation schedules, or CRM write-back. Document creation through the product assistant can still be token-intensive. The free page states that guidance before you continue.

What becomes paid?

Pay per document is public web create with checkout when prepaid credit is not in use. Sign in through Pay per doc to use that path. The price charged at checkout is the live checkout amount. It is not restated as a fixed figure on this page.

Organisation prepaid credit is the staff workspace at internal.officemaker.ai. Creates debit the organisation wallet. If the balance is empty, the product reports: Your organisation has no prepaid credit. Add credit to create. Top-up amounts, seat fees and auto top-up thresholds are visible to the organisation after sign-in.

The authenticated document service adds the verbs the free sandbox omits: merge into an existing file, sequential edit, Office-to-PDF and related conversion, deterministic Excel query and keyed update, workflows, connections and document management, subject to the tenant’s entitlements. Education and corporate licences are quoted. Use the form on this page or contact OfficeMaker.

MCP and API use the same metering

MCP is a way for an assistant to call the document service. REST is a way for an application to call it. On the free host, schema-led create is not billed through either door. On a paid or organisation host, MCP tools run the same balance precheck and debit as the matching REST verbs. Connecting ChatGPT or Claude by MCP does not waive document-service charges and does not move a paid verb onto the free sandbox.

A structured create where the caller supplies the complete document JSON meters document rendering. That call does not, by itself, run OfficeMaker’s own document-generation model. Merge, edit, conversion and Excel search are separate paid verbs with their own metering on authenticated hosts.

Assistant model charges are a separate component

When ChatGPT, Claude, or another provider authors the structured JSON, that provider bills model usage on the account you hold with them. OfficeMaker does not fold an OpenAI or Anthropic invoice into the free sandbox, and a ChatGPT subscription is not an OfficeMaker plan.

OfficeMaker’s own signed-in Create assistant is a different path. The product performs the generation, and pay-per-document checkout or the organisation prepaid wallet applies. An organisation wallet is the OfficeMaker usage balance. It is not a substitute invoice for a model provider unless your quoted agreement says otherwise. This page does not describe a bundle that includes third-party model tokens.

Which option fits?

Choose from the path that matches how often you generate files and whether you need verbs beyond create.

Developer prototype — free sandbox for schema discovery, gap analysis and unpaid create of new Office files.
Occasional document generation — pay per document on the public site when you are not drawing an organisation wallet.
Production API or MCP — authenticated document service so merge, edit, conversion and Excel query are available, with metering on that host.
Internal corporate workflow — an organisation tenant with automations, approval, storage and optional Salesforce, usually under a quoted licence. See corporate deployment.
High-volume automation — organisation prepaid credit, with amounts shown after sign-in, or a quoted corporate agreement. This page does not publish a volume-discount table.

Evidence behind this

Pricing statements on this page describe paths the product already exposes. Amounts that vary by organisation are left to sign-in or a quote.

Free create is not billed

Claim. The public sandbox does not bill schema-led create and does not require an API key.

Mechanism. free.officemaker.ai serves the narrow create, preview, schema and gap-analysis surface.

Evidence. Developer resources

Limitation. Free create is rate-limited and excludes merge, edit, macros and conversion.

Paid hosts meter MCP and REST together

Claim. MCP does not bypass document-service charges on a paid or organisation host.

Mechanism. The document service applies the same prepaid precheck to MCP tools as to REST, then debits on successful paid work.

Evidence. MCP document generation

Limitation. Wallet size, seat fees and quoted licence prices are organisation-specific and are not listed here.

Middleware and token use

Claim. Doing file work outside the model can reduce unnecessary token use.

Mechanism. Parsing, filtering, calculation, validation and file construction happen in OfficeMaker middleware, so the model works with relevant structured state rather than a rendering program or a screenshot loop.

Evidence. Token-efficiency workflow write-up (15 April 2026)

Limitation. The published figures are reasoned estimates for one PowerPoint workflow, about 60,000–90,000 tokens for a Python/PptxGenJS path with image review versus about 20,000–30,000 for OfficeMaker on that example. Savings vary by document size, workflow and model. They are not a billing guarantee.

Contact OfficeMaker about a quote · Open developer resources · free.officemaker.ai

Questions

Does MCP avoid OfficeMaker charges?: No. MCP and REST use the same document-generation backend. Free-host create is not billed. Paid and organisation hosts meter MCP calls the same way they meter the matching REST verbs.
Are ChatGPT or Claude charges included in OfficeMaker?: No. When those products author the structured JSON, the model provider bills that usage separately. OfficeMaker meters document-service work. Pay-per-document checkout and organisation prepaid credit apply to OfficeMaker usage, including the signed-in Create assistant. They are not an OpenAI or Anthropic subscription.
Where are seat fees and prepaid amounts shown?: After you sign in to the relevant workspace, or in a quote for education and corporate licences. This page does not invent those figures.