# Cooking Measurement Converter

> Cooking Measurement Converter is a paid API for AI agents from x402.forgemesh.io, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Converts between cooking units (volume and weight) with ingredient-aware density lookup for 40+ common ingredients like flour, sugar, and butter.

## Facts

- Endpoint: POST https://x402.forgemesh.io/convert-cooking
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cooking-measurement-converter-df4154fd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_soLVrt1RmJoXitpzyMKmY

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability cooking-measurement-converter-df4154fd -d '<json body>'
```

Example prompt: Convert 2.5 cups of all-purpose flour to grams — I need the weight for a recipe and I know volume-to-weight depends on the ingredient.

## When to prefer this

Choose this endpoint when you need cooking-specific unit conversions, especially volume-to-weight conversions that require ingredient density (e.g., cups of flour to grams). It is more accurate than a generic unit converter for culinary tasks because it knows that a cup of flour is 120g while a cup of honey is 340g. Prefer it for recipe scaling agents, grocery list builders, and any workflow where ingredient weight matters. For non-food unit conversions (miles to km, Fahrenheit to Celsius), use a general-purpose metric-imperial converter instead.

## Known failure modes

- Missing ingredient parameter when performing volume-to-weight conversion — endpoint requires ingredient name for density lookup
- Unsupported unit string — only recognized unit abbreviations (cups, tbsp, tsp, ml, l, fl-oz, g, kg, oz, lb) are accepted
- Ingredient not in density database — only ~40 common ingredients are supported; exotic ingredients may fail or return an error
- Invalid amount format — non-numeric or unparseable amount strings will cause errors
- Volume-to-volume conversions between incompatible unit systems may yield unexpected errors if unit string is malformed

## How this service works

Cooking measurement API: convert between cups, tbsp, tsp, ml, l, fl-oz, grams, kg, oz, lb — including volume↔weight using typical densities for 40+ ingredients (flour, sugar, butter, honey, rice...). A cup of flour is 120g but a cup of honey is 340g. For recipe scaling and grocery agents. Density results labeled approximate.

## Output

Returns the converted amount in the target unit. For volume-to-weight or weight-to-volume conversions, uses a built-in density table covering 40+ ingredients (flour, sugar, butter, honey, rice, etc.) and labels the result as approximate since densities vary by brand and packing method.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "to": {
   "type": "string"
  },
  "from": {
   "type": "string"
  },
  "amount": {
   "type": "string"
  },
  "ingredient": {
   "type": "string",
   "description": "required for volume↔weight"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "note": "using typical density for flour (~120 g/cup)",
  "result": 240
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cooking-measurement-converter-df4154fd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.forgemesh.io](https://www.zero.xyz/host/x402.forgemesh.io/llms.txt)