# Additive Atlas Label Diff Analyzer

> Additive Atlas Label Diff Analyzer is a paid API for AI agents from api.additiveatlas.monon.space, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-16).

Parses a food label's additive/ingredient text and returns cross-jurisdiction regulatory derivations for each identified additive across JP, EU, and US axes

## Facts

- Endpoint: POST https://api.additiveatlas.monon.space/v1/labels/analyze/diff?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/additive-atlas-label-diff-analyzer-a8190e49
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_d_GLFTSZWdsonEmjrp-aZ

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 additive-atlas-label-diff-analyzer-a8190e49 -d '<json body>'
```

Example prompt: I've got the ingredients section from a Japanese food label — can you find all the additives in it and show me how each one is regulated differently in the EU and US? The label language is Japanese and the regulatory axis is JP.

## When to prefer this

Use this endpoint when you have a raw food label text and need to identify multiple additives at once with a full cross-jurisdiction regulatory comparison in a single call. Prefer this over the single-substance sibling endpoint when processing entire ingredient sections rather than one known additive name. Best suited for compliance workflows, import/export regulatory checks, and consumer-facing food transparency tools.

## Known failure modes

- Unsupported axis+language combination returns an error referencing the GET / scopes endpoint
- Non-additive ingredient text may yield no identified additives
- Ambiguous or proprietary ingredient names may not resolve to a known additive
- Malformed or empty text input returns a validation error
- Unknown ISO 639-1 language code results in a bad request error

## How this service works

Find the additives named on a food label and return, for each, the cross-axis derivation across jurisdictions

## Output

A structured response containing each identified additive from the label text, with cross-axis derivation data showing how that substance is regulated under each of the other major jurisdictions (JP, EU, US, Codex, IAR), enabling side-by-side regulatory comparison.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "axis": {
   "enum": [
    "JP",
    "US",
    "EU"
   ],
   "type": "string",
   "description": "Regulatory axis the label is written for"
  },
  "lang": {
   "type": "string",
   "description": "Language of the label text (ISO 639-1). Accepted axis+lang pairs are listed by GET / under scopes"
  },
  "text": {
   "oneOf": [
    {
     "type": "string"
    },
    {
     "type": "array",
     "items": {
      "type": "string"
     }
    }
   ],
   "description": "The additive (or whole ingredient) section of one label: one raw string, or an array of already-split items"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/additive-atlas-label-diff-analyzer-a8190e49/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.additiveatlas.monon.space](https://www.zero.xyz/host/api.additiveatlas.monon.space/llms.txt)