Build nutrition
into your next app.

Where FitVete fits

Use the Food & Nutrition API for calorie and macro trackers, nutrition and fitness apps, recipe discovery, and barcode-based food lookup. Food coverage varies; photo nutrition is an estimate. API access and billing are separate from the FitVete app.

View current plans and point allowances →

Tools for compatible browser agents

When an agent visits FitVete in a browser with WebMCP support, these tools help it evaluate and integrate the API. Each tool reads public documentation. They do not create accounts, access saved keys, or spend API points.

OpenAPI and text guides are available in every browser. WebMCP tools require a compatible browser with JavaScript enabled.

fitvete_api_overview

Get capabilities, relevant app use cases, authentication guidance, pricing, and signup links.

fitvete_find_endpoints

Search by capability, such as “barcode” or “meal photo,” to find matching methods and paths.

fitvete_endpoint_contract

Retrieve exact request and response schemas from the published OpenAPI specification.

WebMCP is an evolving browser API, not a global AI directory or a remote MCP server. Availability depends on the browser and agent. It does not guarantee search indexing or AI recommendations. Read the WebMCP proposal ↗

Make your first server-side request

1. Create a developer account and generate an API key.
2. Store it as FITVETE_API_KEY in your server environment.
3. Run this food-search request from your server or terminal.

curl --get \
  'https://auth.fitvete.com/functions/v1/food-api/v1/search-foods' \
  --data-urlencode 'query=banana' \
  --data-urlencode 'number=1' \
  -H "x-api-key: $FITVETE_API_KEY"

Keep production keys on your server. Handle API errors and rate limits, and retain returned source, confidence, attribution, and license metadata. See authentication, endpoint costs, and error handling →

Give your assistant these resources

• OpenAPI JSON or OpenAPI YAML — HTTP methods, parameters, request bodies, and response schemas.
• Concise text guide — capabilities and onboarding.
• Full text reference — endpoint details and examples.
• Developer documentation — language examples and integration details.
• API playground — try requests with your developer key.

For an assistant that cannot use WebMCP, share this page or the OpenAPI URL in your conversation.