# Klarys

> Klarys (formerly ProcSea; legal entity Procsea SA, Rennes, France) is a SaaS eProcurement platform for
> the fresh-food supply chain — seafood, fruit and vegetables, meat and dairy — connecting retail,
> wholesale and foodservice buyers with their suppliers, wholesalers and mareyeurs. Klarys markets API and
> EDI integration with customer ERP, accounting and product-reference systems. Its tenant application runs
> at klarys.app and publishes an RFC 8414 OAuth 2.0 authorization-server metadata document anonymously,
> but no public API reference, OpenAPI document or developer portal.

GENERATED by API Evangelist, not published by Klarys. Klarys serves no llms.txt of its own
(https://www.klarys.io/llms.txt -> 404, https://klarys.app/llms.txt -> 302 to the app shell), so this file
is assembled from the company's public surface and from the artifacts in this repository. Checked
2026-08-17.

## What an agent can and cannot do here

- There is NO public machine-readable contract. A schema endpoint exists at
  https://klarys.app/api/schema/ but returns HTTP 401 to anonymous callers
  (`{"code":1003,"error":"User is unauthenticated"}`) with Content-Type
  `application/vnd.oai.openapi+json` — the OpenAPI is real and customer-gated.
- The OAuth 2.0 authorization server IS public and machine-readable, including its scope list.
- Klarys advertises `mcp:read` and `mcp:write` scopes, so a Model Context Protocol surface exists, but no
  MCP endpoint is anonymously discoverable and no RFC 9728 protected-resource metadata is served.
- No A2A agent card, no security.txt, no OpenID Connect discovery, no published rate limits, no pricing.

## Machine-readable surface

- [OAuth 2.0 authorization server metadata (RFC 8414)](https://klarys.app/.well-known/oauth-authorization-server): HTTP 200 application/json. Issuer `https://klarys.app/api/public/o`. Grants: authorization_code, client_credentials, refresh_token. PKCE S256. Dynamic client registration, revocation and introspection endpoints. Scopes: groups, introspection, mcp:read, mcp:write, read, write.
- [Same document under the issuer path](https://klarys.app/api/public/o/.well-known/oauth-authorization-server): HTTP 200.

## Product

- [Solutions](https://www.klarys.io/en/solutions): supplier interface, centralized purchasing interface, central purchasing module, supplier invoicing module, business-intelligence module, standardized fresh-food catalog. States the platform "integrates with all your business systems and applications via API and EDI".
- [Why Klarys](https://www.klarys.io/en/features)
- [Case studies](https://www.klarys.io/en/case-studies)
- [Who are we](https://www.klarys.io/en/who-are-we)
- [Customer service](https://www.klarys.io/en/service-client)
- [Contact / book a demo](https://www.klarys.io/en/contact)

## Operations

- [Status page](https://status.klarys.io/): provider-owned subdomain, redirects to a Notion page titled "Klarys status page". Renders client-side; no machine-readable status feed.
- [Terms of service](https://www.klarys.io/en/terms-of-service): Article 4.8.b references the "programming interface ('API') made available through the Site or the Platform". Article 12.1 states availability "cannot be guaranteed" — no SLA, no uptime target.
- [Privacy policy](https://www.klarys.io/en/privacy-policy)
- [Legal notice](https://www.klarys.io/en/legal-notice)
- [Log in](https://klarys.app/fr/accounts/login/)

## Code

- [GitHub organization](https://github.com/procsea) — org login `procsea`, display name "Klarys", Rennes France, 2 public repositories. No API client library.
- [django-remove-field](https://pypi.org/project/django-remove-field/) — first-party Django utility (author "Klarys Tech Team", tech@klarys.io), v0.3.0, published 2025-11-26. Not an SDK for the Klarys API.

## Content

- [Resources / articles](https://www.klarys.io/en/resources)
- [Press](https://www.klarys.io/en/press)
- [ProcSea becomes Klarys](https://www.klarys.io/en/articles/procsea-becomes-klarys) — the rename.
- [Joining GS1, a must](https://www.klarys.io/en/articles/joining-gs1-a-must) — GS1 partnership.
- [SAP Store listing](https://store.sap.com/dcp/en/product/display-0000060188_live_v1/procsea-digitize-your-food-procurement-process) — SAP.iO partner.

## API Evangelist artifacts in this repository

- authentication/klarys-authentication.yml — OAuth 2.0 profile, probed from the RFC 8414 document.
- scopes/klarys-scopes.yml — the six published scopes.
- well-known/klarys-well-known.yml — full /.well-known probe, 1 hit and 15 misses.
- conformance/klarys-conformance.yml — 7 standards conformant, 5 absent, 4 claimed-unverified.
- errors/klarys-problem-types.yml — the observed proprietary error envelope plus the OAuth error envelope.
- conventions/klarys-conventions.yml — runtime semantics observed live; no idempotency evidence.
- lifecycle/klarys-lifecycle.yml — status page, no versioning/deprecation policy, no SLA.
- mcp/klarys-mcp.yml — the MCP scope finding and every endpoint probe that missed.
- packages/klarys-packages.yml — registries checked; no client library exists.
- plans/klarys-plans-pricing.yml — plan_count 0, contact-sales.
- rate-limits/klarys-rate-limits.yml — limit_count 0, no runtime signal.
- security/klarys-domain-security.yml — TLS/HSTS/DNSSEC/CAA/SPF/DMARC probe.