Klarys

Klarys — formerly ProcSea, renamed in 2023 — is a French SaaS eProcurement platform built for the fresh-food supply chain: seafood, fruit and vegetables, meat and dairy. It connects retail, wholesale and foodservice buyers with their suppliers, wholesalers and mareyeurs through a standardized fresh-food product catalog, a supplier sales interface, a centralized purchasing interface, a central purchasing module for store networks, a supplier invoicing module and a business-intelligence module. Klarys states that the platform "integrates with all your business systems and applications via API and EDI" — ERP, accounting tools and product reference systems. Founded in 2016 in Rennes, France with operations in Switzerland, it is a Serena portfolio company, a member of the SAP.iO acceleration program and listed on the SAP Store. The tenant application runs at klarys.app and publishes an RFC 8414 OAuth 2.0 authorization-server metadata document anonymously — including mcp:read and mcp:write scopes — but no public API reference, OpenAPI, or developer portal: the schema endpoint requires an authenticated tenant account.

Klarys publishes 1 API on the APIs.io network. Tagged areas include Company, Software-as-a-Service, eProcurement, Procurement, and Supply Chain.

Klarys’ developer surface includes support, engineering blog, legal docs, YouTube channel, authentication, and 23 more developer resources.

🌐 Visit website 📡 Source on GitHub

20.7/100 emerging ▬ flat Agent 21/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

AccessApproval

1 APIs

Company Software-as-a-Service eProcurement Procurement Supply Chain Food and Beverage SeafoodFresh FoodRetail EDI Invoicing France

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 20.7/100 · emerging

Contract Quality 0.0 / 25

Developer Ergonomics 3.8 / 20

Access Clarity 5.5 / 20

Operational Transparency 2.4 / 13

Contract Governance 2.2 / 12

Discoverability 6.9 / 10

Agent readiness — 21/100 · agent aware

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 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 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 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

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.

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 github.com/api-evangelist/klarys: open an issue to ask a question, or submit a pull request to add artifacts. 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.

Klarys Platform API

The API surface behind the Klarys tenant application at klarys.app. Klarys markets API and EDI integration with customer ERP, accounting and product-reference systems, and the a...

Pricing Plans 1

Published pricing tiers and plan structures.

Klarys Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Klarys Rate Limits

0 limits

RATE LIMITS

Security Posture 2

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

Klarys Authentication

oauth2 · 1 scheme

SECURITY

Klarys Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Klarys Scopes

6 scopes · authorizationCode/clientCredentials

6 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

Login

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Conventions

Lifecycle

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

OAuthScopes

OAuthScopes

Learn 1

Tutorials, courses, talks, and written guidance

Youtube

Youtube

Operate 4

Status, limits, changes, and where to get help

Support

Contact

StatusPage

RateLimits

Commercial 4

Pricing, plans, and the legal terms of use

TermsOfService

PrivacyPolicy

Legal

Plans

Company 6

The organization behind the API

Website

Blog

Press

About

LinkedIn

Twitter

Twitter

Other 1

Properties that don't map to a standard resource type

CaseStudies

CaseStudies

Source (apis.yml)

aid: klarys
name: Klarys
description: 'Klarys — formerly ProcSea, renamed in 2023 — is a French SaaS eProcurement platform built for the fresh-food
  supply chain: seafood, fruit and vegetables, meat and dairy. It connects retail, wholesale and foodservice buyers with their
  suppliers, wholesalers and mareyeurs through a standardized fresh-food product catalog, a supplier sales interface, a centralized
  purchasing interface, a central purchasing module for store networks, a supplier invoicing module and a business-intelligence
  module. Klarys states that the platform "integrates with all your business systems and applications via API and EDI" — ERP,
  accounting tools and product reference systems. Founded in 2016 in Rennes, France with operations in Switzerland, it is
  a Serena portfolio company, a member of the SAP.iO acceleration program and listed on the SAP Store. The tenant application
  runs at klarys.app and publishes an RFC 8414 OAuth 2.0 authorization-server metadata document anonymously — including mcp:read
  and mcp:write scopes — but no public API reference, OpenAPI, or developer portal: the schema endpoint requires an authenticated
  tenant account.'
url: https://raw.githubusercontent.com/api-evangelist/klarys/refs/heads/main/apis.yml
x-api-posture: no-product-api
x-api-posture-basis: observed
x-api-posture-note: The tenant application runs at klarys.app and publishes an RFC 8414 OAuth 2.0 authorization-server metadata
  document anonymously — including mcp:read and mcp:write scopes — but no public API reference
x-type: company
x-source: serena-portfolio
x-tier: stub
x-tier-reason: portfolio-lead
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: approval
  trial: false
  try_now: false
  public: false
  label: Requires approval
  confidence: medium
  source:
  - plans
  - authentication
  - scopes
  - rate-limits
  - security
  generated: '2026-09-03'
  method: derived
specificationVersion: '0.23'
created: '2026-08-17'
modified: '2026-08-17'
image: https://cdn.prod.website-files.com/645262ac6eca60aef2a6ff24/6487761d3ac838e6ec321735_klarys%20the%20fresh%20food%20platform.webp
tags:
- Company
- Software-as-a-Service
- eProcurement
- Procurement
- Supply Chain
- Food and Beverage
- Seafood
- Fresh Food
- Retail
- EDI
- Invoicing
- France
tags_raw:
- Company
- SaaS
- eProcurement
- Procurement
- Supply Chain
- Food and Beverage
- Seafood
- Fresh Food
- Retail
- EDI
- Invoicing
- France
apis:
- name: Klarys Platform API
  description: 'The API surface behind the Klarys tenant application at klarys.app. Klarys markets API and EDI integration
    with customer ERP, accounting and product-reference systems, and the application serves an anonymous RFC 8414 OAuth 2.0
    authorization-server metadata document at https://klarys.app/.well-known/oauth-authorization-server (issuer https://klarys.app/api/public/o)
    with authorization_code, client_credentials and refresh_token grants, PKCE S256, dynamic client registration, token revocation
    and introspection. No public API reference, OpenAPI document or developer portal was found: the schema endpoint at https://klarys.app/api/schema/
    returns HTTP 401 {"code":1003,"error":"User is unauthenticated"}, so the contract is customer-gated.'
  humanURL: https://www.klarys.io/en/solutions
  baseURL: https://klarys.app/api/
  tags:
  - eProcurement
  - Supply Chain
  - Fresh Food
  properties:
  - type: Authentication
    url: authentication/klarys-authentication.yml
  - type: OAuthScopes
    url: scopes/klarys-scopes.yml
  - type: ErrorCatalog
    url: errors/klarys-problem-types.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/klarys-domain-security.yml
- type: Website
  url: https://www.klarys.io/
- type: Support
  url: https://www.klarys.io/en/service-client
- type: Contact
  url: https://www.klarys.io/en/contact
- type: Blog
  url: https://www.klarys.io/en/resources
- type: Press
  url: https://www.klarys.io/en/press
- type: CaseStudies
  url: https://www.klarys.io/en/case-studies
- type: About
  url: https://www.klarys.io/en/who-are-we
- type: GitHubOrganization
  url: https://github.com/procsea
- type: Login
  url: https://klarys.app/fr/accounts/login/
- type: TermsOfService
  url: https://www.klarys.io/en/terms-of-service
- type: PrivacyPolicy
  url: https://www.klarys.io/en/privacy-policy
- type: Legal
  url: https://www.klarys.io/en/legal-notice
- type: StatusPage
  url: https://status.klarys.io/
- type: LinkedIn
  url: https://www.linkedin.com/company/klarys/
- type: Twitter
  url: https://twitter.com/klarys_io
- type: Youtube
  url: https://www.youtube.com/@klarys_io
- type: WellKnown
  url: well-known/klarys-well-known.yml
- type: Authentication
  url: authentication/klarys-authentication.yml
- type: OAuthScopes
  url: scopes/klarys-scopes.yml
- type: Conformance
  url: conformance/klarys-conformance.yml
- type: ErrorCatalog
  url: errors/klarys-problem-types.yml
- type: Conventions
  url: conventions/klarys-conventions.yml
- type: Lifecycle
  url: lifecycle/klarys-lifecycle.yml
- type: Packages
  url: packages/klarys-packages.yml
- type: LLMsTxt
  url: llms/klarys-llms.txt
- type: Plans
  url: plans/klarys-plans-pricing.yml
- type: RateLimits
  url: rate-limits/klarys-rate-limits.yml
x-enrichment:
  date: '2026-08-17'
  status: minimal
  artifacts_added: 14
  pass: local-v1
x-coverage:
  state: gated
  reason: customer-only-docs
  detail: Klarys runs a Django REST Framework API with a live OpenAPI schema endpoint, but https://klarys.app/api/schema/?format=json
    answers HTTP 401 {"code":1003,"error":"User is unauthenticated"} with Content-Type application/vnd.oai.openapi+json —
    the spec is real and served only to an authenticated tenant, and there is no developer portal, API reference or pricing
    page anywhere on www.klarys.io (all 134 sitemap URLs walked).
  evidence:
  - url: https://klarys.app/api/schema/?format=json
    status: 401
  - url: https://klarys.app/.well-known/oauth-authorization-server
    status: 200
  - url: https://www.klarys.io/llms.txt
    status: 404
  - url: https://klarys.app/.well-known/oauth-protected-resource
    status: 404
  checked: '2026-08-17'

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/klarys"

All providers

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

Every operation they expose

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

How their score was established

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

Discovery needs no key. Ratings and market analysis are Pro.

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.