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 APIs on the APIs.io network, including catalog API, connect_customers API, general API, and 2 more. Tagged areas include Company, Food, Wholesale, Ordering, and Restaurants.

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

🌐 Visit website 📡 Source on GitHub
36.9/100 thin ▬ flat Agent 65/100 agent native Full breakdown ↓
scored 2026-07-27 · rubric v0.5
AccessSelf serve
5 APIs 1 MCP Servers
CompanyFoodWholesaleOrderingRestaurantsSupply ChainCatalogOrderseCommerce

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 36.9/100 · thin
Contract Quality 9.4 / 25
Developer Ergonomics 12.6 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 65/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 12 / 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
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/rekki: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

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.

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

rekki-mcp.yml

MCP SERVER

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 · 27 acting

32 operations · 27 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
 MCPServer
MCPServer
 LLMsTxt
LLMsTxt
 AgentSkill
AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conformance
Conformance
 ErrorCatalog
ErrorCatalog
 Lifecycle
Lifecycle
 Conventions
Conventions
 DataModel
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 1

Properties that don't map to a standard resource type

Overlay
Overlay

Source (apis.yml)

apis.yml Raw ↑ 
aid: rekki
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  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.20'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- 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
  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:
  - 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:
  - 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:
  - 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: 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: MCPServer
  url: mcp/rekki-mcp.yml
- 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