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.

5.0/100 minimal ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
0 APIs
CompanyFood and BeverageFoodPortfolio CompanyVenture BackedGeneral CatalystPre-Launch

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
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/eeki-foods: 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 →

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

Company 1

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: eeki-foods
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
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.23'
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.

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/eeki-foods"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/eeki-foods/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/eeki-foods/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.

A second provider on the same verified email joins the account you already have.