Remberg
remberg is a Munich-based B2B SaaS provider of an Intelligent Asset Platform for maintenance, operations, and service — CMMS/EAM/CAFM software used by industrial companies (Vaillant, Remondis, Liqui Moly, SCHUNK, EDEKA, OSRAM) to manage assets, work orders, spare parts, tickets, forms, and preventive maintenance, with an AI Copilot and a lightweight execution layer alongside SAP. remberg exposes a public REST API (api.remberg.de) across Assets, Work Orders, Work Requests, Tickets, Parts, Organizations, Contacts, Users, Files, Forms, Procedures, and AI, with API-key auth, Svix-based webhooks, documented rate limits, and ISO 27001 certification.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Remberg the way a machine reads it — 26 machine-readable artifacts across 19 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Remberg scores 48.2/100 (developing), with a separate agent-readiness read of 82/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Remberg
Each block below is one kind of artifact we hold for Remberg. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 19
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Remberg ai-chat API
The ai-chat API from Remberg — 2 operation(s) for ai-chat.
Remberg asset-status-signals API
The asset-status-signals API from Remberg — 5 operation(s) for asset-status-signals.
Remberg asset-types API
The asset-types API from Remberg — 3 operation(s) for asset-types.
Remberg assets API
The assets API from Remberg — 5 operation(s) for assets.
Remberg contacts API
The contacts API from Remberg — 2 operation(s) for contacts.
Remberg failure-types API
The failure-types API from Remberg — 2 operation(s) for failure-types.
Remberg files API
The files API from Remberg — 6 operation(s) for files.
Remberg forms API
The forms API from Remberg — 2 operation(s) for forms.
Remberg inventories API
The inventories API from Remberg — 4 operation(s) for inventories.
Remberg organizations API
The organizations API from Remberg — 4 operation(s) for organizations.
Remberg part-stock-changes API
The part-stock-changes API from Remberg — 2 operation(s) for part-stock-changes.
Remberg parts API
The parts API from Remberg — 3 operation(s) for parts.
Remberg procedure-templates API
The procedure-templates API from Remberg — 1 operation(s) for procedure-templates.
Remberg tickets API
The tickets API from Remberg — 4 operation(s) for tickets.
Remberg user-groups API
The user-groups API from Remberg — 1 operation(s) for user-groups.
Remberg user-roles API
The user-roles API from Remberg — 1 operation(s) for user-roles.
Remberg users API
The users API from Remberg — 3 operation(s) for users.
Remberg work-orders API
The work-orders API from Remberg — 12 operation(s) for work-orders.
Remberg work-requests API
The work-requests API from Remberg — 7 operation(s) for work-requests.
Scroll within the panel for all 19 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
remberg-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Remberg Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Remberg Events Webhooks
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Remberg — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 7
MCP servers, agent skills, and machine-readable catalogs
Scroll within the panel for all 7 ·
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/remberg · machine-readable index on apis.io