Source: https://billingmart.com/features/assistants [Features](https://billingmart.com/features) Let software do the typing • Model Context Protocol & AI # AI That Drafts — You Decide What Goes Out Drafts from a description, and an API an assistant can hold — both of which stop short of sending. [Start using Let software do the typing](https://app.billingmart.com/sign-up) [← All 8 product stages](https://billingmart.com/features) Model Context Protocol • Human approval guardrail ## Connect AI Agents Safely with Official MCP Claude, ChatGPT, and Gemini connect natively via our streamable HTTP Model Context Protocol endpoint. The assistant reads, drafts and asks; a request goes ahead only once a signed-in person, or the workspace owner’s capped rule for a connection the owner put in Auto approves it. Try Interactive Prompts: Enforced Platform Capabilities ## Included in Let software do the typing Every feature below is active in production and enforced by server transactions. The plan each one starts on is the published one; every plan is on [the pricing page](https://billingmart.com/pricing) . ### AI Studio #### Invoice template designer Describe the layout; the preview is drawn by the real renderer. A draft until a person publishes it. Server verified ai-templates #### Pay page designer Emits colour values, never CSS, and every one is checked for contrast in both themes before it can be published. Server verified ai-pay-page #### Assistive copy Reminder text, line descriptions and payment-plan explanations. Plain text only — tags and links are refused. Server verified ai-copy #### Business model generator Describe your trade and get a proposed set of terms, presets and invoice fields — every field editable before it saves. Server verified ai-business-model ### API and assistants #### REST API and API keys Every operation under one OpenAPI document, scoped per key. Server verified api-rest #### Hosted MCP server Connect an AI assistant to your billing. It reads, drafts, records and asks: in Ask, the default, a signed-in person approves each request; Plan is a dry run; in Auto, which only the owner can switch on with a second factor, on a plan with auto-approve rules, the owner’s capped rule approves what it covers. For a connected assistant, refunds, voids, card or bank entry and the other never-auto requests still wait for a person. Server verified api-mcp #### Auto-approve rules The owner writes capped rules — kind, amount, count a day — and a matching action runs at once, with the connection as actor. For a connected assistant, refunds, voids, card or bank entry and the other never-auto requests still wait for a person; the built-in Agent, in Auto on its own person’s grant, may run some of them under the owner’s rule. Server verified agent-auto #### Outbound webhooks HMAC-signed, retried and dead-lettered, with the destination re-resolved on every delivery. Server verified api-webhooks #### Approvals inbox What an assistant asks for waits here, out of its reach, for a person to approve it, unless the connection is in Auto and the owner’s capped rule covers the request. Server verified approvals Next Stage in Product Walk ## Run the workspace: Multi-Business, Multi-User Control Businesses, people, roles and the settings that decide what each of them may do. [Continue to Run the workspace →](https://billingmart.com/features/workspace) ## Ready to start with Let software do the typing? Start on the free plan and stay there as long as it fits. Move up as your billing grows. [Start free](https://app.billingmart.com/sign-up) [Compare all plans](https://billingmart.com/pricing#compare) --- This is the Markdown copy of https://billingmart.com/features/assistants. Live plans, prices and limits are published as JSON at https://billingmart.com/plans.json and https://billingmart.com/agent-info.json.