Rimsys

Rimsys is a Regulatory Information Management (RIM) platform purpose-built for medical device and MedTech manufacturers. It centralizes regulatory submissions, global product registrations, Unique Device Identification (UDI) management, standards and GSPR maintenance, regulatory intelligence, impact assessments, and market-access operations in a single system of record. Rimsys exposes enterprise APIs and an event-driven change-data-capture layer (Rimsys Connect) to integrate regulatory data with PLM, ERP, QMS, CRM, and BI tools, and provides direct EUDAMED/GUDID UDI transmission. Developer documentation is published at docs.rimsys.io.

Rimsys is listed with 1 API on the APIs.io network. Tagged areas include Company, Vertical Software, Regulatory, Medical Devices, and Medical Technology.

Rimsys’ developer surface includes documentation, API reference, pricing, support, engineering blog, signup flow, authentication, and 14 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

34.7/100 thin ▬ flat Agent 3/100 human only Front door AI 6/6 dominant Heartbeat 48/100 going silent saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API

Company Vertical Software Regulatory Medical Devices Medical TechnologyRegulatory Information ManagementUDICompliance Life Sciences

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 34.7/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 7.7 / 17

Access Clarity 10.3 / 17

Operational Transparency 2.0 / 11

Contract Governance 1.9 / 10

Discoverability 6.2 / 9

Regulatory Posture 3.5 / 15

Agent readiness — 3/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

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 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/rimsys/"><img src="https://apis.io/badge/rimsys/card.svg" alt="Rimsys on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0

12 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Developer Ergonomics scores 45.2 — up to +11.0 composite points
Operational Transparency scores 18.4 — up to +10.6 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/rimsys/apis.yml: open an issue on github.com/api-evangelist/rimsys to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Canada Medical Device Licensing (Health Canada MDALL licence holders, incl. SaMD)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

APIs 1

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

Rimsys API

Enterprise API for the Rimsys Regulatory Information Management platform, used to integrate regulatory submissions, product registrations, UDI data, standards, and regulatory in...

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Rimsys

SLA

Security Posture 3

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

Rimsys Authentication

http · 1 scheme

SECURITY

Rimsys Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Rimsys Trust Center

SOC 2, ISO 27001, GDPR, 21 CFR Part 11

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

SignUp

SignUp

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Lifecycle

Lifecycle

Conformance

Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 4

Authentication, authorization, and security posture

TrustCenter

Compliance

Authentication

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Website

Website

Blog

Blog

LinkedIn

Source (apis.yml)

aid: rimsys
name: Rimsys
description: Rimsys is a Regulatory Information Management (RIM) platform purpose-built for medical device and MedTech manufacturers.
  It centralizes regulatory submissions, global product registrations, Unique Device Identification (UDI) management, standards
  and GSPR maintenance, regulatory intelligence, impact assessments, and market-access operations in a single system of record.
  Rimsys exposes enterprise APIs and an event-driven change-data-capture layer (Rimsys Connect) to integrate regulatory data
  with PLM, ERP, QMS, CRM, and BI tools, and provides direct EUDAMED/GUDID UDI transmission. Developer documentation is published
  at docs.rimsys.io.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://cdn.prod.website-files.com/69c2116a63e9aeb725071337/6a3248583da864ec36ccd531_OG%20rimsys.png
url: https://raw.githubusercontent.com/api-evangelist/rimsys/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- bessemer-venture-partners
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Vertical Software
- Regulatory
- Medical Devices
- Medical Technology
- Regulatory Information Management
- UDI
- Compliance
- Life Sciences
tags_raw:
- Company
- Vertical Software
- Regulatory
- Medical Devices
- MedTech
- Regulatory Information Management
- UDI
- Compliance
- Life Sciences
apis:
- name: Rimsys API
  description: Enterprise API for the Rimsys Regulatory Information Management platform, used to integrate regulatory submissions,
    product registrations, UDI data, standards, and regulatory intelligence with PLM, ERP, QMS, CRM, and BI systems. Documentation
    is published on the Rimsys developer portal (Theneo-hosted); requests are authenticated with a bearer access token.
  humanURL: https://docs.rimsys.io/
  baseURL: https://api.rimsys.io/
  tags:
  - Regulatory
  - Medical Devices
  - Integration
  properties:
  - type: Documentation
    url: https://docs.rimsys.io/
  - type: APIReference
    url: https://docs.rimsys.io/
  - type: Authentication
    url: authentication/rimsys-authentication.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.rimsys.io/
- type: DeveloperPortal
  url: https://docs.rimsys.io/
- type: Documentation
  url: https://docs.rimsys.io/
- type: APIReference
  url: https://docs.rimsys.io/
- type: Integrations
  url: https://www.rimsys.io/integrations/integrations
- type: Pricing
  url: https://www.rimsys.io/pricing
- type: Support
  url: https://www.rimsys.io/support
- type: Blog
  url: https://www.rimsys.io/blogs
- type: SignUp
  url: https://www.rimsys.io/demo
- type: Login
  url: https://app.rimsys.io/
- type: TermsOfService
  url: https://www.rimsys.io/legal/terms-of-service
- type: PrivacyPolicy
  url: https://www.rimsys.io/legal/privacy-policy
- type: GitHubOrganization
  url: https://github.com/Rimsys
- type: LinkedIn
  url: https://www.linkedin.com/company/rimsys/
- type: StatusPage
  url: https://status.rimsys.io/
- type: TrustCenter
  url: security/rimsys-trust-center.yml
- type: Compliance
  url: https://www.rimsys.io/security-compliance
- type: LLMsTxt
  url: llms/rimsys-llms.txt
- type: Authentication
  url: authentication/rimsys-authentication.yml
- type: Lifecycle
  url: lifecycle/rimsys-lifecycle.yml
- type: Conformance
  url: conformance/rimsys-conformance.yml
- type: DomainSecurity
  url: security/rimsys-domain-security.yml
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 7
  pass: local-v1

Rimsys API — frequently asked questions

Does Rimsys have an API?

Yes. APIs.io lists 1 API from Rimsys, including Rimsys API.

How do I authenticate with the Rimsys API?

Rimsys uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Rimsys Authentication.

Is the Rimsys API ready for AI agents?

Rimsys has a Kin Score of 34.7 out of 100 (thin) and an Agent Readiness score of 2.5 (human-only), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/rimsys"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/rimsys/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/rimsys/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.