Ermeo

Ermeo (rebranded Causeway Field) is a French connected-operator / field-operations SaaS platform that lets industrial and field teams digitize paper procedures into dynamic, interactive workflows for inspections, maintenance, and interventions. Operators complete pre-built interactive forms on mobile, capture equipment and report data in the field in real time, and operational managers monitor all field work from a central console. Ermeo exposes a REST API secured with OAuth 2.0 so customers can connect their information systems (CMMS, MES, EDM) to import and synchronize equipment, forms, and reports and enrich the data collected in the field.

Ermeo publishes 1 API on the APIs.io network. Tagged areas include Company, Field Service Management, Connected Operator, Field Operations, and Industrial.

Ermeo’s developer surface includes API reference, documentation, getting-started guide, support, engineering blog, authentication, and 7 more developer resources.

18.0/100 emerging ▬ flat Agent 14/100 human only Full breakdown ↓
scored 2026-07-23 · rubric v0.5
AccessSelf serve
1 APIs
CompanyField Service ManagementConnected OperatorField OperationsIndustrialMaintenanceInspectionsSaaS

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-23 · rubric v0.5
Composite quality — 18.0/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 8.7 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 9.3 / 10
Agent readiness — 14/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/ermeo: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Ermeo API

REST API for the Ermeo connected-operator platform. Authenticated with OAuth 2.0 (Bearer access tokens), it lets external systems read and write equipment, forms, reports, and f...

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Ermeo Authentication

oauth2 · 1 scheme

SECURITY

Ermeo Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Access & Security 2

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: ermeo
name: Ermeo
description: Ermeo (rebranded Causeway Field) is a French connected-operator / field-operations SaaS platform that lets industrial
  and field teams digitize paper procedures into dynamic, interactive workflows for inspections, maintenance, and interventions.
  Operators complete pre-built interactive forms on mobile, capture equipment and report data in the field in real time, and
  operational managers monitor all field work from a central console. Ermeo exposes a REST API secured with OAuth 2.0 so customers
  can connect their information systems (CMMS, MES, EDM) to import and synchronize equipment, forms, and reports and enrich
  the data collected in the field.
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://www.ermeo.com/en/
url: https://raw.githubusercontent.com/api-evangelist/ermeo/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- partech
x-tier: stub
x-tier-reason: portfolio-lead
x-acquired-by: Causeway Technologies
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Field Service Management
- Connected Operator
- Field Operations
- Industrial
- Maintenance
- Inspections
- SaaS
apis:
- name: Ermeo API
  description: REST API for the Ermeo connected-operator platform. Authenticated with OAuth 2.0 (Bearer access tokens), it
    lets external systems read and write equipment, forms, reports, and field data so customers can integrate Ermeo with their
    CMMS, MES, and EDM information systems.
  humanURL: https://ermeo.stoplight.io/
  baseURL: https://api.ermeo.com
  tags:
  - API
  - Field Operations
  - OAuth2
  properties:
  - type: APIReference
    url: https://ermeo.stoplight.io/
  - type: Authentication
    url: authentication/ermeo-authentication.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.ermeo.com/en/
- type: APIReference
  url: https://ermeo.stoplight.io/
- type: Documentation
  url: https://support.en.ermeo.com/login-to-ermeo-api-and-send-requests
- type: GettingStarted
  url: https://support.en.ermeo.com/getting-started-with-ermeo
- type: Support
  url: https://support.en.ermeo.com/
- type: Blog
  url: https://www.ermeo.com/en/blog/
- type: Authentication
  url: authentication/ermeo-authentication.yml
- type: Conventions
  url: conventions/ermeo-conventions.yml
- type: Lifecycle
  url: lifecycle/ermeo-lifecycle.yml
- type: Conformance
  url: conformance/ermeo-conformance.yml
- type: WellKnown
  url: well-known/ermeo-well-known.yml
- type: DomainSecurity
  url: security/ermeo-domain-security.yml
- type: LLMsTxt
  url: llms/ermeo-llms.txt
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence