Introduction
Overview of bitERP, available environments, and how to obtain credentials for integration.
What is bitERP?
bitERP is an AI-first ERP (Enterprise Resource Planning) system, designed as a multi-tenant SaaS platform. It lets companies manage products, customers, suppliers, orders, finances, and more — all with native integration to AI agents.
Integration channels
| Channel | Protocol | Audience | Authentication |
|---|---|---|---|
| Integrations API | REST (JSON) | External systems, automations (Zapier, Make, n8n) | API Keys or OAuth2 |
| MCP Server | Model Context Protocol (JSON-RPC) | AI agents (Claude, GPT, etc.) | OAuth2 via Clerk |
Environments
| Environment | API Base URL | MCP Base URL |
|---|---|---|
| Production | https://api.biterp.ai | https://mcp.biterp.ai |
Obtaining credentials
API Keys (for the Integrations API)
- Sign in to the bitERP dashboard at app.biterp.ai
- Go to Settings > API Keys
- Click Create API Key
- Set the name, description, and per-resource permissions
- Copy the token immediately — it is shown only once
The token has the format sk_<id>_<secret>.
OAuth2 (for automations and MCP)
For OAuth2 integrations (Zapier, Make, n8n) or to connect AI agents via MCP, authentication uses the OAuth2 Authorization Code flow. See the authentication section of each channel for details.
Core concepts
Multi-tenancy
Each company in bitERP is an isolated tenant. Every operation runs in the context of a specific tenant:
- API Keys: each key belongs to a single tenant — the context is automatic
- OAuth2/MCP: the agent must call
list_tenantsfirst and pass thetenant_idon operations
Permissions
bitERP uses a granular permission model per resource and action (create, read, update, delete). Each API Key or OAuth user has specific permissions configured by the administrator.
Data isolation
Data from different tenants is fully isolated via Row-Level Security (RLS) in the database. It is not possible to access another tenant's data, even with valid credentials.