LogMeal
LogMeal provides a Food Recognition Image API that detects foods, drinks, vegetables, fruits and prepared dishes from images. The platform offers semantic tagging including food group, dish and ingredients recognition, as well as nutritional information analysis with 35+ nutritional indicators and user intake history tracking.
LogMeal publishes 3 APIs on the APIs.io network: History API, Image Recognition API, and Nutrition API. Tagged areas include Computer-Vision, Food, Image Recognition, Nutrition, and Semantic Tagging.
LogMeal’s developer surface includes authentication, documentation, developer portal, engineering blog, and 5 more developer resources.
Kin Score
APIs 3
Individual APIs this provider publishes, each with its own machine-readable definition.
LogMeal History API
Retrieve a user's logged food intakes over time.
LogMeal Image Recognition API
Detect food items in user-submitted images.
LogMeal Nutrition API
Retrieve ingredients and nutritional information for confirmed intakes.
Open Collections 5
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONLogMeal Food Recognition API
OPEN COLLECTIONLogMeal Food Recognition History API
OPEN COLLECTIONLogMeal Food Recognition History Image Recognition API
OPEN COLLECTIONLogMeal Food Recognition History Nutrition API
OPEN COLLECTIONPricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Logmeal Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Logmeal Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Access & Security 2
Authentication, authorization, and security posture
Company 3
The organization behind the API
Source (apis.yml)
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/providers/logmeal"
curl "https://apis.io/api/v1/providers?limit=25"
curl "https://apis.io/api/v1/providers/logmeal/operations?limit=25"
curl "https://apis.io/api/v1/providers/logmeal/evidence"
Discovery needs no key. Ratings and market analysis are Pro.