What InBlack is
InBlack is a tenant-scoped business operating platform organized around Accounting, Commerce, Studio, Customer 360, Reporting, Portal, and the newer Data X substrate capability.
Product responsibilities
| Product | Responsibility |
|---|---|
| Accounting | Ledger, banking, receivables, payables, tax, close, and financial reports |
| Commerce | Catalog, channels, inventory, orders, returns, suppliers, purchasing, and assemblies |
| Studio | Sites, forms, email templates, redirects, webhooks, domains, and SDK/API keys |
| Customer 360 | Contacts, companies, segments, health projections, and customer analysis |
| Reporting | Dashboards, report templates, custom reports, schedules, and data exploration |
| Portal | Tenant membership, roles, billing, onboarding, integrations, and practice links |
| Data X | User-defined tables and records behind the Data X entitlement |
Availability depends on tier, role, entitlement, feature configuration, and the maturity of each product route. A page in the UI is not proof that every displayed action is backed by a write handler; the operator guides call out those boundaries.
Delivery surfaces
- Product SPAs are the human operator surfaces and call product APIs.
- MCP at
https://ai-coo.inblack.app/mcpis the default agent surface. - GraphQL and HTTP APIs support product UIs, integrations, storefronts, provider callbacks, and documented ADR-0019 carve-outs.
- Agentic Commerce UCP and ACP routes provide signed commerce protocol surfaces separate from tenant MCP.
These surfaces share tenant and authorization concepts but do not have one universal request, error, approval, or audit envelope. Use the contract for the surface being called.
Start with The three surfaces, Plans, tiers, and entitlements, or the persona-specific guide for SMB operators, accountants, and developers.
Loading index…