REKKI

REKKI is a food wholesale ordering platform that connects restaurants and chefs (buyers) with their suppliers. Restaurants place orders through the REKKI app, and suppliers receive, confirm, and fulfil them. REKKI publishes a public Supplier API that lets suppliers programmatically manage their product catalog (items, inventory, price lists), receive and confirm orders, report integration status back to REKKI, and manage REKKI Connect customers and their order guides. Authentication uses a supplier bearer token plus an X-REKKI-Authorization-Type header. REKKI's current product suite also includes AI agents for wholesale distributors (OrderAI, InboxAI, MenuAI) and a Marketplace. REKKI was surfaced as a portfolio company of Creandum and Point Nine.

REKKI publishes 5 API contracts indexed on the APIs.io network, including Catalog API, Connect Customers API, General API, and 2 more. Tagged areas include Company, Food, Wholesale, Ordering, and Restaurant.

The REKKI catalog on APIs.io includes 1 Spectral governance ruleset.

REKKI’s developer surface includes getting-started guide, support, documentation, API reference, authentication, and 18 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

39.7/100 developing ▬ flat Agent 23/100 agent aware Front door AI 4/6 moderate Heartbeat 54/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 2 Agent Skills

Company Food Wholesale Ordering Restaurant Supply Chain Catalog Order E-Commerce

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Customer Relationship Management

BC-420

connect_customers

Kin Score

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

Composite quality — 39.7/100 · developing

Contract Quality 7.7 / 19

Developer Ergonomics 8.1 / 15

Access Clarity 3.2 / 15

Operational Transparency 0.3 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 3.7 / 15

Create-or-Update Ergonomics 3.9 / 10

Agent readiness — 23/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 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 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 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 0 / 5

Distinct Operations 0 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) 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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% 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/rekki/"><img src="https://apis.io/badge/rekki/card.svg" alt="REKKI 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):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
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)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

10 more unmet checks in the Agent Readiness table above.

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

Access Clarity scores 21.1 — up to +15.8 composite points
Contract Quality scores 40.9 — up to +14.8 composite points
Operational Transparency scores 2.6 — up to +12.7 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/rekki/apis.yml: open an issue on github.com/api-evangelist/rekki 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 →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 5

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

REKKI Catalog API

The catalog API from REKKI — 12 operation(s) for catalog.

REKKI Connect Customers API

The connect_customers API from REKKI — 2 operation(s) for connect_customers.

REKKI General API

The general API from REKKI — 2 operation(s) for general.

REKKI Order Guide API

The order-guide API from REKKI — 1 operation(s) for order-guide.

REKKI Orders API

The orders API from REKKI — 11 operation(s) for orders.

Open Collections 5

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Rekki.com Supplier catalog API

OPEN COLLECTION

Rekki.com Supplier catalog connect_customers API

OPEN COLLECTION

Rekki.com Supplier catalog general API

OPEN COLLECTION

Rekki.com Supplier catalog order-guide API

OPEN COLLECTION

Rekki.com Supplier catalog orders API

OPEN COLLECTION

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Process restaurant orders from REKKI

AGENT SKILL

Sync a supplier catalog to REKKI

AGENT SKILL

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

REKKI API Rules

62 rules · 54 errors 7 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Rekki Supplier Api Overlay

2 actions · documentation · rekki-supplier-api-openapi-original.json

DERIVED

Security Posture 2

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

Rekki Authentication

apiKey · 1 scheme

SECURITY

Rekki Domain Security

TLSv1.2 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Rekki Agentic Access

32 operations · 23 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

DataModel

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 1

The organization behind the API

Website

Website

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: rekki
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - 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://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/rekki.png
name: REKKI
description: REKKI is a food wholesale ordering platform that connects restaurants and chefs (buyers) with their suppliers.
  Restaurants place orders through the REKKI app, and suppliers receive, confirm, and fulfil them. REKKI publishes a public
  Supplier API that lets suppliers programmatically manage their product catalog (items, inventory, price lists), receive
  and confirm orders, report integration status back to REKKI, and manage REKKI Connect customers and their order guides.
  Authentication uses a supplier bearer token plus an X-REKKI-Authorization-Type header. REKKI's current product suite also
  includes AI agents for wholesale distributors (OrderAI, InboxAI, MenuAI) and a Marketplace. REKKI was surfaced as a portfolio
  company of Creandum and Point Nine.
url: https://raw.githubusercontent.com/api-evangelist/rekki/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- creandum
- point-nine
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Food
- Wholesale
- Ordering
- Restaurant
- Supply Chain
- Catalog
- Order
- E-Commerce
tags_raw:
- Company
- Food
- Wholesale
- Ordering
- Restaurants
- Supply Chain
- Catalog
- Orders
- eCommerce
apis:
- aid: rekki:rekki-catalog-api
  name: REKKI Catalog API
  description: The catalog API from REKKI — 12 operation(s) for catalog.
  humanURL: https://api.rekki.com/swagger/index.html
  baseURL: https://api.rekki.com
  tags:
  - Catalog
  tags_raw:
  - catalog
  properties:
  - type: OpenAPI
    url: openapi/rekki-catalog-api-openapi.yml
  - type: Documentation
    url: https://github.com/rekki/supplier-api
  - type: APIReference
    url: https://api.rekki.com/swagger/index.html
- aid: rekki:rekki-connect-customers-api
  name: REKKI Connect Customers API
  description: The connect_customers API from REKKI — 2 operation(s) for connect_customers.
  humanURL: https://api.rekki.com/swagger/index.html
  baseURL: https://api.rekki.com
  tags: []
  tags_raw:
  - connect_customers
  properties:
  - type: OpenAPI
    url: openapi/rekki-connect-customers-api-openapi.yml
  - type: Documentation
    url: https://github.com/rekki/supplier-api
  - type: APIReference
    url: https://api.rekki.com/swagger/index.html
- aid: rekki:rekki-general-api
  name: REKKI General API
  description: The general API from REKKI — 2 operation(s) for general.
  humanURL: https://api.rekki.com/swagger/index.html
  baseURL: https://api.rekki.com
  tags: []
  tags_raw:
  - general
  properties:
  - type: OpenAPI
    url: openapi/rekki-general-api-openapi.yml
  - type: Documentation
    url: https://github.com/rekki/supplier-api
  - type: APIReference
    url: https://api.rekki.com/swagger/index.html
- aid: rekki:rekki-order-guide-api
  name: REKKI Order Guide API
  description: The order-guide API from REKKI — 1 operation(s) for order-guide.
  humanURL: https://api.rekki.com/swagger/index.html
  baseURL: https://api.rekki.com
  tags:
  - order-guide
  properties:
  - type: OpenAPI
    url: openapi/rekki-order-guide-api-openapi.yml
  - type: Documentation
    url: https://github.com/rekki/supplier-api
  - type: APIReference
    url: https://api.rekki.com/swagger/index.html
- aid: rekki:rekki-orders-api
  name: REKKI Orders API
  description: The orders API from REKKI — 11 operation(s) for orders.
  humanURL: https://api.rekki.com/swagger/index.html
  baseURL: https://api.rekki.com
  tags:
  - Order
  tags_raw:
  - orders
  properties:
  - type: OpenAPI
    url: openapi/rekki-orders-api-openapi.yml
  - type: Documentation
    url: https://github.com/rekki/supplier-api
  - type: APIReference
    url: https://api.rekki.com/swagger/index.html
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/rekki-capability-edges.yml
  name: REKKI Business Capability Map
- type: Website
  url: https://rekki.com/
- type: GettingStarted
  url: https://rekki.com/suppliers
- type: Support
  url: https://rekki.com/faq
- type: TermsOfService
  url: https://rekki.com/terms-and-conditions
- type: PrivacyPolicy
  url: https://tandc.rekki.com/
- type: GitHubOrganization
  url: https://github.com/rekki
- type: Documentation
  url: https://github.com/rekki/supplier-api
- type: APIReference
  url: https://api.rekki.com/swagger/index.html
- type: Authentication
  url: authentication/rekki-authentication.yml
- type: DomainSecurity
  url: security/rekki-domain-security.yml
- type: AgenticAccess
  url: agentic-access/rekki-agentic-access.yml
- type: Packages
  url: packages/rekki-packages.yml
- type: SDKs
  url: packages/rekki-packages.yml
- type: X-MCPServerCandidate
  url: mcp/rekki-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/rekki-llms.txt
- type: Overlay
  url: overlays/rekki-supplier-api-overlay.yaml
- type: Conformance
  url: conformance/rekki-conformance.yml
- type: ErrorCatalog
  url: errors/rekki-problem-types.yml
- type: Lifecycle
  url: lifecycle/rekki-lifecycle.yml
- type: Conventions
  url: conventions/rekki-conventions.yml
- type: DataModel
  url: data-model/rekki-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 14
  pass: local-v1

REKKI API — frequently asked questions

Does REKKI have an API?

Yes. APIs.io lists 5 APIs from REKKI, including REKKI Catalog API, REKKI Connect Customers API and REKKI General API, and 2 more.

Is there an OpenAPI specification for the REKKI API?

Yes. APIs.io indexes 5 OpenAPI specifications for REKKI, each linked for download from this page.

How do I authenticate with the REKKI API?

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

Is the REKKI API ready for AI agents?

REKKI has a Kin Score of 39.7 out of 100 (developing) and an Agent Readiness score of 22.6 (agent-aware), 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/rekki"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/rekki/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.