How it works

Apps use REST. Agents use MCP. AgentGrid runs the repeatable work.

Slab5 keeps the operational boundary in one place: workspace data, credentials, scopes, workflow runs, approvals, audit logs, usage events, and billing controls.

Request access Read the docs

Your app or websiteServer-side integration, portal, internal tool, or marketing site.

Workspace API keyExplicit scopes such as crm:write, cms:read, support:write.

Slab5 workspace

One business tool plane

Business tools, Data & Insights, audit, usage, billing, credentials, notifications, and workspace controls.

ChatGPT, Claude, or another agentContent drafts, CRM updates, support triage, tasks, and analysis.

MCP client or OAuth grantTool access limited to the same workspace and module scopes.

AgentGrid workflowReusable runs with schedules, approval gates, retries, logs, and outputs.

Workflow policyAgents, tool allowlists, risk limits, approvals, resource caps, and audit context.

Same recordsSame scopesSame audit logSame usage meterSame run history

Application path

Use REST APIs from your server-side app code

Your product, portal, internal tool, or website calls Slab5 with a workspace-scoped API key. The key carries explicit scopes, so the integration only reaches the business tools it needs.

Server-side API calls only

Workspace-scoped API keys

CRM, CMS, support, tasks, files, projects, products, calendar, notifications, and webhook objects

Agent path

Use MCP tools from ChatGPT, Claude, or another agent

Agents connect through scoped MCP clients or OAuth grants. They can draft content, inspect CRM and support context, create tasks, store artifacts, and call allowed tools without direct database access.

Workspace-scoped MCP clients

Module and tool-level permissions

Every important action can be audited

Workflow path

Use AgentGrid when the work needs approvals, schedules, retries, and run history

AgentGrid turns agent and tool work into reusable workflow definitions with published versions, run logs, approval gates, duration history, failure handling, and operational visibility.

Run workflows manually or on hourly, daily, weekly, and monthly schedules

Approve, reject, retry, cancel, or continue workflow runs

Inspect step state, generated outputs, tool calls, retrieval hits, costs, request IDs, and errors