# Cooking Measurement Converter (Ingredient-Aware)

> Cooking Measurement Converter (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-13).

Converts cooking measurements between volume and weight units (cups, tablespoons, ml, grams, oz) using ingredient-specific densities for 40+ ingredients.

## Facts

- Endpoint: POST https://x402.forgemesh.io/cooking-measurements
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cooking-measurement-converter-ingredient-aware-753bea60
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TdkIvzJWxpyb-gJervH_x

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-ingredient-aware-753bea60 -d '<json body>'
```

Example prompt: Can you convert 2.5 cups of flour to grams? I need the ingredient-aware weight, not just a generic volume conversion.

## When to prefer this

Choose this endpoint when you need cooking-specific volume-to-weight or weight-to-volume conversions that depend on ingredient density (e.g. cups of flour vs cups of honey weigh very differently). Prefer it over generic unit converters for kitchen and recipe tasks where ingredient type matters. Use the sibling metric-imperial converter for non-food unit conversions like km to miles.

## Known failure modes

- Unknown ingredient — ingredient not in the 40+ supported list, conversion fails or falls back to generic density
- Missing ingredient field when converting between volume and weight — required for volume↔weight conversions
- Invalid unit strings in 'from' or 'to' fields — unsupported unit names cause errors
- Malformed amount string — non-numeric or unparseable amount values
- Network or payment failure — x402 micropayment of $0.002 USDC not processed

## How this service works

Cooking conversion API: cups↔grams↔tablespoons↔ml with ingredient-aware densities for 40+ ingredients (a cup of flour is 120g, a cup of honey is 340g). The kitchen math LLMs get wrong.

## Output

Returns the converted measurement value in the requested target unit, adjusted for the actual density of the specified ingredient (e.g. acknowledging that a cup of flour is 120g while a cup of honey is 340g).

## 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-ingredient-aware-753bea60/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)