Libryo website screenshot

Libryo

Libryo (ERM Libryo) is a regulatory compliance management platform for Environmental, Health and Safety (EHS) teams. It automates legal registers, streams site-specific regulatory obligations across jurisdictions, and tracks legislative change so that operators know which laws apply to each of their sites. Founded in 2016 with a distributed team across Cape Town, London, Toronto, Nairobi and Berlin, Libryo is now part of ERM, the sustainability consultancy. The product surface spans Libryo Sites (site-specific EHS regulatory intelligence), Libryo Assess (assessment and audit management), Libryo Collaborate, and custom legal registers, and is used in manufacturing, energy and utilities, chemicals, mining, logistics and telecoms. Libryo exposes a partner-facing RESTful API secured with OAuth 2.0 authorization-code flow, documented publicly in the libryo/libryo-api-oauth-docs repository, and also offers its regulatory content as a data-as-a-service feed into third-party GRC platforms.

Libryo is listed with 1 API on the APIs.io network. Tagged areas include Company, Regulatory Compliance, Legal Tech, Environmental Health and Safety, and Governance Risk and Compliance.

Libryo’s developer surface includes engineering blog, documentation, support, pricing, and 19 more developer resources.

27.2/100 thin ▬ flat Agent 5/100 human only Front door AI 2/6 trace Heartbeat 50/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
AccessEnterpriseSelf serve
1 API
CompanyRegulatory ComplianceLegal TechEnvironmental Health and SafetyGovernance Risk and ComplianceLegal RegistersRegulatory Change ManagementSustainabilityAuthentication

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0
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. Kin Score badge preview for Libryo It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/libryo/"><img src="https://apis.io/badge/libryo/card.svg" alt="Libryo 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
11 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
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/libryo/apis.yml: open an issue on github.com/api-evangelist/libryo 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 →

APIs 1

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

Libryo API

The Libryo Platform's partner-facing RESTful API. Third-party applications integrate on behalf of a Libryo user using the OAuth 2.0 authorization-code flow, then call the versio...

Libryo API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Libryo Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Libryo Rate Limits

0 limits

RATE LIMITS

Security Posture 2

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

Libryo Authentication

oauth2 · 1 scheme

SECURITY

Libryo Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Libryo Scopes

3 scopes

3 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 4

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: libryo
name: Libryo
description: Libryo (ERM Libryo) is a regulatory compliance management platform for Environmental, Health and Safety (EHS)
  teams. It automates legal registers, streams site-specific regulatory obligations across jurisdictions, and tracks legislative
  change so that operators know which laws apply to each of their sites. Founded in 2016 with a distributed team across Cape
  Town, London, Toronto, Nairobi and Berlin, Libryo is now part of ERM, the sustainability consultancy. The product surface
  spans Libryo Sites (site-specific EHS regulatory intelligence), Libryo Assess (assessment and audit management), Libryo
  Collaborate, and custom legal registers, and is used in manufacturing, energy and utilities, chemicals, mining, logistics
  and telecoms. Libryo exposes a partner-facing RESTful API secured with OAuth 2.0 authorization-code flow, documented publicly
  in the libryo/libryo-api-oauth-docs repository, and also offers its regulatory content as a data-as-a-service feed into
  third-party GRC platforms.
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: enterprise
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Enterprise · Self-serve signup
  confidence: medium
  probe_state: unreadable
  source:
  - authentication
  - scopes
  - security
  generated: '2026-11-06'
  method: derived
image: https://libryo.com/wp-content/uploads/2025/03/cropped-favicon-32x32.png
url: https://raw.githubusercontent.com/api-evangelist/libryo/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- seedcamp
x-parent-company: ERM
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Regulatory Compliance
- Legal Tech
- Environmental Health and Safety
- Governance Risk and Compliance
- Legal Registers
- Regulatory Change Management
- Sustainability
- Authentication
tags_raw:
- Company
- Regulatory Compliance
- Legal Tech
- Environmental Health and Safety
- Governance Risk and Compliance
- Legal Registers
- Regulatory Change Management
- Sustainability
- OAuth
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Deprecation
  url: lifecycle/libryo-lifecycle.yml
- type: Hosts
  url: hosts/libryo-hosts.yml
- type: Vendors
  url: vendors/libryo-vendors.yml
- type: SDKs
  url: packages/libryo-packages.yml
- type: TermsOfService
  url: https://libryo.com/terms/
- type: Blog
  url: https://blog.libryo.com/what-is-a-legal-register
- type: Website
  url: https://libryo.com
- type: Documentation
  url: https://github.com/libryo/libryo-api-oauth-docs
- type: GitHubOrganization
  url: https://github.com/libryo
- type: Support
  url: https://libryo.com/contact-us/
- type: HelpCenter
  url: https://libryo.com/faqs/
- type: Pricing
  url: https://libryo.com/pricing-regulatory-tracking/
- type: Login
  url: https://my.libryo.com/login
- type: PrivacyPolicy
  url: https://libryo.com/privacy-policy/
- type: CaseStudies
  url: https://libryo.com/case-studies/
- type: Resources
  url: https://libryo.com/resources-legaltech/
- type: About
  url: https://libryo.com/about-us/
- type: Packages
  url: packages/libryo-packages.yml
- type: WellKnown
  url: well-known/libryo-well-known.yml
- type: DomainSecurity
  url: security/libryo-domain-security.yml
- type: Conventions
  url: conventions/libryo-conventions.yml
- type: Conformance
  url: conformance/libryo-conformance.yml
- type: Lifecycle
  url: lifecycle/libryo-lifecycle.yml
apis:
- aid: libryo:libryo-api
  name: Libryo API
  description: The Libryo Platform's partner-facing RESTful API. Third-party applications integrate on behalf of a Libryo
    user using the OAuth 2.0 authorization-code flow, then call the versioned /api/v1 surface to view legal reports, search
    legislation, and list the user's Libryos (site-specific regulatory streams). Libryo publishes the OAuth integration guide
    in a public GitHub repository; the endpoint reference itself is made available to partners under agreement rather than
    published openly.
  humanURL: https://github.com/libryo/libryo-api-oauth-docs
  baseURL: https://api.libryo.com/api/v1
  tags:
  - Regulatory Compliance
  - Legal Registers
  - Legislation Search
  - OAuth
  - Authentication
  tags_raw:
  - Regulatory Compliance
  - Legal Registers
  - Legislation Search
  - OAuth
  - Authentication
  properties:
  - type: Documentation
    url: https://github.com/libryo/libryo-api-oauth-docs
  - type: Authentication
    url: authentication/libryo-authentication.yml
  - type: OAuthScopes
    url: scopes/libryo-scopes.yml
  - type: Conventions
    url: conventions/libryo-conventions.yml
  - type: Lifecycle
    url: lifecycle/libryo-lifecycle.yml
  - type: Conformance
    url: conformance/libryo-conformance.yml
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  detail: Libryo's only public API documentation is a 2017 OAuth authorization-code README on GitHub (my.libryo.com/oauth/authorize,
    api.libryo.com/api/v1/oauth/token); no OpenAPI, endpoint reference, llms.txt or MCP surface is published on any Libryo
    host.
  evidence:
  - url: https://raw.githubusercontent.com/libryo/libryo-api-oauth-docs/master/README.md
    status: 200
  - url: https://libryo.com/pricing-regulatory-tracking/
    status: 200
  checked: '2026-10-20'
x-enrichment:
  date: '2026-10-20'
  status: minimal
  artifacts_added: 2
  pass: local-v5

Libryo API — frequently asked questions

Does Libryo have an API?

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

How do I authenticate with the Libryo API?

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

Is the Libryo API ready for AI agents?

Libryo has a Kin Score of 27.2 out of 100 (thin) and an Agent Readiness score of 5.0 (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/libryo"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/libryo/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/libryo/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.

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