Jefe
Jefe ("Jefe para restaurantes", chejefe.com) is a SaaS platform for restaurants in Spanish-speaking Latin America, operated by AticoVentures, LLC (Florida, US) and founded in Argentina in 2026. It runs an AI agent that takes orders over WhatsApp, a branded online store, and an order backoffice that sends each ticket to the kitchen, plus WhatsApp marketing and franchise insights, so restaurants can sell through a direct channel instead of depending on delivery marketplaces. For developers and agents it publishes a read-only public API with an OpenAPI specification, Markdown page representations, an llms.txt index, NLWeb search and a Streamable HTTP MCP server.
Jefe publishes 4 API contracts indexed on the APIs.io network, including Guides API, NL Web API, Product API, and 1 more. Tagged areas include Company, Restaurant, WhatsApp, Food Ordering, and Artificial Intelligence.
The Jefe catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.
Jefe’s developer surface includes documentation, API reference, support, engineering blog, pricing, and 35 more developer resources.
Kin Score
Kin Score
How this is scored →scored 2026-11-13 · rubric v0.28.0
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/chejefe-com/"><img src="https://apis.io/badge/chejefe-com/card.svg" alt="Jefe on APIs.io — Kin Score by API Evangelist"></a>Other styles, a README pill and a shields.io endpoint are on the badge page.
- Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey) Ask about this →
- Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
- A2A Agent Card +8 pts — a2a/
-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this → - Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →
- Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented) Ask about this →
- Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks Ask about this →
- Developer Ergonomics scores 42.3 — up to +11.5 composite points Ask about this →
- Contract Quality scores 60.1 — up to +10.0 composite points Ask about this →
- Operational Transparency scores 26.2 — up to +9.6 composite points Ask about this →
Standards implemented 2
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
APIs 4
Individual APIs this provider publishes, each with its own machine-readable definition.
Jefe Guides API
Catálogo editorial publicado.
Jefe NL Web API
Búsqueda natural stateless sobre guías públicas.
Jefe Product API
Identidad y capacidades públicas verificables.
Jefe Resources API
Recursos oficiales para agentes.
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
Jefe MCP Server
Official public, read-only Streamable HTTP MCP server for Jefe ("Jefe para restaurantes"). Per its own instructions it only returns public, verifiable information about Jefe and...
MCP SERVERAgent Skills 2
Packaged agent skills for driving this provider's APIs from an AI assistant.
describe-jefe-product
AGENT SKILLresearch-jefe-guides
AGENT SKILLJefe API pricing
Prices published by Jefe.
| Plan | Price |
|---|---|
| Canal directo | desde 5% de comisión por pedido |
| API pública y MCP | API pública y MCP: gratuitos, anónimos y de sólo lectura para contenido ya publicado |
Plan details, limits and sources →
Rate limits
- Abusive or excessive request limiting: Jefe puede limitar solicitudes abusivas o excesivas y responder 429
Pricing Plans 1
Published pricing tiers and plan structures.
Jefe Plans Pricing
PLANSRate Limits 1
Documented rate limits and quota policies.
Jefe Rate Limits
RATE LIMITSTerms of Service 1
What its API terms permit and prohibit, quoted from its own page.
Privacy & Data 1
Its role, the data it processes, retention and transfers, quoted from its own privacy page.
Eligibility 1
Who may sign up and where, quoted from its own terms.
AI Preferences 1
Its stance on AI training, inference and agents, quoted from its own pages.
Data License 1
How its data and outputs may be reused, quoted from its own terms.
Semantic Vocabularies 1
JSON-LD contexts and semantic vocabularies used across these APIs.
Chejefe Com Context
JSON-LDSpectral Rules 1
Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.
Jefe API Rules
SPECTRALOpenAPI Overlays 1
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
Jefe Openapi Overlay
DERIVEDJSON Schema 6
Standalone JSON Schema definitions for this provider's data models.
GuideDetail
JSON SCHEMAGuideList
JSON SCHEMANlWebRequest
JSON SCHEMANlWebResponse
JSON SCHEMAProduct
JSON SCHEMAResourceList
JSON SCHEMASecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access (API Evangelist recommendations) 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll for all 8
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 6
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 5
Properties that don't map to a standard resource type
Source (apis.yml)
Jefe API — frequently asked questions
Does Jefe have an API?
Yes. APIs.io lists 4 APIs from Jefe, including Jefe Guides API, Jefe NL Web API and Jefe Product API, and 1 more.
Is there an OpenAPI specification for the Jefe API?
Yes. APIs.io indexes 4 OpenAPI specifications for Jefe, each linked for download from this page.
How do I authenticate with the Jefe API?
Jefe documents its authentication (0 schemes). The details are profiled on APIs.io as Jefe Authentication.
How much does the Jefe API cost?
Jefe publishes its prices; its Canal directo plan is desde 5% de comisión por pedido as of 2026-11-03. APIs.io lists 2 pricing plans for Jefe, with each plan's price, limits and inclusions under Pricing on this page.
Does Jefe have an MCP server?
Yes. APIs.io lists 1 MCP server for Jefe: Official public, read-only Streamable HTTP MCP server for Jefe ("Jefe para restaurantes"). Per its own instructions it only returns public, verifiable information about Jefe and its published guides;
Is the Jefe API ready for AI agents?
Jefe has a Kin Score of 49.4 out of 100 (developing) and an Agent Readiness score of 34.7 (agent-ready), scored by API Evangelist on 2026-11-13.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.