# Cooking Measurement Converter (Volume & Weight, Ingredient-Aware)

> Cooking Measurement Converter (Volume & Weight, Ingredient-Aware) 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-15).

Converts cooking measurements between volume and weight units using ingredient-specific densities, so a cup of flour and a cup of honey each convert to their correct, different gram weights.

## Facts

- Endpoint: POST https://x402.forgemesh.io/cups-to-grams
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cooking-measurement-converter-volume-weight-ingredient-aware-ff34bbc5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FsO7Xc26injh9phtEF_cf

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-volume-weight-ingredient-aware-ff34bbc5 -d '<json body>'
```

Example prompt: Can you convert 2.5 cups of all-purpose flour to grams for my bread recipe?

## When to prefer this

Choose this endpoint when you need ingredient-aware cooking measurement conversions, especially volume-to-weight (e.g. cups to grams) where generic unit converters fail because they don't account for ingredient density. Prefer this over a generic unit conversion API whenever the ingredient matters for accuracy — flour, butter, honey, and water all have different gram weights per cup. Also ideal for baking and recipe-scaling agents that must handle mixed measurement systems.

## Known failure modes

- Unrecognized ingredient name — API may return an error or fall back to a default density
- Missing ingredient field when converting between volume and weight — required for those conversion types
- Invalid unit strings for 'from' or 'to' fields — must use supported unit identifiers (cups, tbsp, tsp, ml, l, fl-oz, g, kg, oz, lb)
- Amount not parseable as a numeric string — conversion cannot proceed
- Attempting volume-to-volume or weight-to-weight conversions may not require ingredient but still need valid unit codes

## How this service works

Converts cooking measurements between volume units (cups, tbsp, tsp, ml, l, fl-oz) and weight units (g, kg, oz, lb), using ingredient-specific densities so a cup of flour and a cup of honey convert to their correct, different gram weights. For baking apps and recipe-scaling agents.

## Output

Returns the converted measurement value in the requested target unit, applying ingredient-specific density factors so that volume-to-weight conversions accurately reflect the actual mass of the specified ingredient (e.g. flour vs honey vs water each yield different gram values per cup).

## 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-volume-weight-ingredient-aware-ff34bbc5/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)