Eeki Foods website screenshot

Eeki Foods

Eeki Foods is a food company listed in the General Catalyst portfolio and tracked in the API Evangelist network as a portfolio lead. As of the July 2026 enrichment pass the company publishes no public developer surface: eekifoods.com serves a pre-launch "Launching Soon" placeholder page, there are no api./docs./developer. subdomains in DNS, no /.well-known/ discovery documents, no llms.txt, no first-party client libraries on npm or PyPI, and no GitHub organization or repositories. The domain is held and mail-enabled (Google Workspace MX) and serves valid TLS 1.3 with HSTS, so this remains a live lead worth re-checking once the company launches a public product surface.

Eeki Foods is profiled on the APIs.io network. Tagged areas include Company, Food and Beverage, Food, Portfolio Company, and Venture Backed.

🌐 Visit website 📡 Source on GitHub
6.8/100 minimal ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-07-27 · rubric v0.5
0 APIs
CompanyFood and BeverageFoodPortfolio CompanyVenture BackedGeneral CatalystPre-Launch

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 6.8/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 0.0 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 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/eeki-foods: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

Security Posture 1

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

Eeki Foods Domain Security

TLSv1.3 · HSTS

SECURITY

Resources

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity
DomainSecurity

Company 1

The organization behind the API

Website
Website

Source (apis.yml)

apis.yml Raw ↑ 
aid: eeki-foods
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/eeki-foods.png
name: Eeki Foods
description: 'Eeki Foods is a food company listed in the General Catalyst portfolio and tracked in the API Evangelist network
  as a portfolio lead. As of the July 2026 enrichment pass the company publishes no public developer surface: eekifoods.com
  serves a pre-launch "Launching Soon" placeholder page, there are no api./docs./developer. subdomains in DNS, no /.well-known/
  discovery documents, no llms.txt, no first-party client libraries on npm or PyPI, and no GitHub organization or repositories.
  The domain is held and mail-enabled (Google Workspace MX) and serves valid TLS 1.3 with HSTS, so this remains a live lead
  worth re-checking once the company launches a public product surface.'
url: https://raw.githubusercontent.com/api-evangelist/eeki-foods/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- general-catalyst
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- Food and Beverage
- Food
- Portfolio Company
- Venture Backed
- General Catalyst
- Pre-Launch
apis: []
common:
- type: DomainSecurity
  url: security/eeki-foods-domain-security.yml
- type: Website
  url: https://www.eekifoods.com
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-07-20'
  status: minimal
  artifacts_added: 2
  pass: local-v1
  notes: No API surface found. WebSearch quota was exhausted this session, so discovery ran via direct HTTP probes (site fetch,
    /.well-known/, llms.txt, subdomain DNS, npm/PyPI/GitHub registry APIs) rather than search-engine queries. Re-run once
    the site launches.