Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Foodology website screenshot

Foodology

Foodology is a Bogota-based food-tech company building what it calls the largest group of delivery-focused virtual restaurant brands in Latin America. Founded in 2019 by Daniela Izquierdo and Juan Guillermo Azuero, it operates a cloud-kitchen (ghost kitchen) model, creating restaurant brands from scratch and running them out of shared commissaries and kitchens so multiple brands share real estate, ingredients, and staff. Marquee brands include Brunch & Munch (the #1 breakfast delivery brand in Colombia) and Avocalia (a leading salad brand). Foodology runs more than 85 cloud kitchens across Colombia, Mexico, Brazil, and Peru and reports over 300,000 delivered orders per month. It is backed by Andreessen Horowitz (a16z), Base10/Base Partners, Wollef, Kayyak, Chimera, and artist Maluma, having raised a $15M Series A and a later $50M round. This profile was surfaced as an a16z portfolio company and added to the API Evangelist network; Foodology is a consumer food-delivery operator and does not publish a public developer API, SDKs, or developer portal.

human only

Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.

Kin Score

API Evangelist profiles Foodology the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Foodology scores 8.9/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 8.9/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 0.0 / 20
Commercial Clarity 2.1 / 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

How we profile Foodology

Each block below is one kind of artifact we hold for Foodology. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

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

Foodology Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for Foodology — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Access & Security 1

Authentication, authorization, and security posture

Commercial 1

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/foodology · machine-readable index on apis.io