Fudo
Fudo is a cloud-based point-of-sale and restaurant management platform used by more than 25,000 restaurants, bars, and cafes across Latin America. The product covers on-premise and online sales, QR menus, kitchen display, inventory and purchasing, expenses, table and room management, staff roles, and delivery-app integrations (Uber Eats, Rappi, PedidosYa). Fudo publishes a general-purpose public REST API (OpenAPI 3.1, JSON:API style) that lets Pro-plan accounts read and write sales, payments, products, customers, expenses, ingredients, and system configuration for reporting, BI, ERP, and custom integrations. This profile was surfaced as an a16z portfolio company and enriched by the API Evangelist pipeline from Fudo's own developer surface.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Fudo the way a machine reads it — 22 machine-readable artifacts across 19 APIs, 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 — Fudo scores 42.9/100 (thin), with a separate agent-readiness read of 46/100 (agent ready). 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
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Fudo
Each block below is one kind of artifact we hold for Fudo. 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.
APIs 19
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Fudo Customers API
The Customers API from Fudo — 2 operation(s) for customers.
Fudo Discounts API
The Discounts API from Fudo — 2 operation(s) for discounts.
Fudo Expense Categories API
The Expense Categories API from Fudo — 2 operation(s) for expense categories.
Fudo Expenses API
The Expenses API from Fudo — 2 operation(s) for expenses.
Fudo Ingredients API
The Ingredients API from Fudo — 2 operation(s) for ingredients.
Fudo Items API
The Items API from Fudo — 2 operation(s) for items.
Fudo Kitchens API
The Kitchens API from Fudo — 2 operation(s) for kitchens.
Fudo Payment Methods API
The Payment Methods API from Fudo — 2 operation(s) for payment methods.
Fudo Payments API
The Payments API from Fudo — 2 operation(s) for payments.
Fudo Product Categories API
The Product Categories API from Fudo — 2 operation(s) for product categories.
Fudo Product Modifiers API
The Product Modifiers API from Fudo — 2 operation(s) for product modifiers.
Fudo Products API
The Products API from Fudo — 2 operation(s) for products.
Fudo Providers API
The Providers API from Fudo — 2 operation(s) for providers.
Fudo Roles API
The Roles API from Fudo — 2 operation(s) for roles.
Fudo Rooms API
The Rooms API from Fudo — 2 operation(s) for rooms.
Fudo Sales API
The Sales API from Fudo — 2 operation(s) for sales.
Fudo Subitems API
The Subitems API from Fudo — 1 operation(s) for subitems.
Fudo Tables API
The Tables API from Fudo — 2 operation(s) for tables.
Fudo Users API
The Users API from Fudo — 2 operation(s) for users.
Scroll within the panel for all 19 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
fudo-mcp.yml
MCP SERVERSecurity Posture 2
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.
Resources
Every other property we hold for Fudo — 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.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/fudo · machine-readable index on apis.io