# BRAINIAC Incoterms Obligation Extractor

> BRAINIAC Incoterms Obligation Extractor is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.04/call, status unknown (last checked 2026-11-11).

Extracts and interprets Incoterms obligations from trade documents or text, identifying buyer/seller responsibilities, risk transfer points, and compliance gaps.

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/freight-customs/incoterms-obligation-extract?utm_source=zero.xyz
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-incoterms-obligation-extractor-577417f7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0I_fhp9uaftQhZr7WGgvw

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 brainiac-incoterms-obligation-extractor-577417f7 -d '<json body>'
```

Example prompt: Can you analyze this purchase order PDF and extract the Incoterms obligations — specifically the rule (like FOB or CIF), the named place, and what the buyer vs seller is responsible for, flagging anything missing like the Incoterms year?

## When to prefer this

Use this endpoint when you need to programmatically extract and interpret Incoterms obligations from raw trade documents or contract text without setting up an account or subscription. It is particularly well-suited for agents processing freight agreements, purchase orders, or bills of lading on a per-document basis and needing structured buyer/seller obligation data with explicit compliance gap findings. It does not perform duty calculations or customs filings, so pair with a customs tariff API when duty rates are needed.

## Known failure modes

- Document text too long or file too large — exceeds maxLength limits
- Incoterms rule not found in document — returns status 'incomplete' with relevant findings
- Named place not identifiable — returned as unavailable
- Incoterms year absent — flagged in findings but not assumed
- Unsupported file media type — only PDF and plain text accepted
- Malformed base64 file encoding — request rejected

## How this service works

Pay-per-call APIs for AI agents: OFAC sanctions screening, compliance checks, token security, and Base chain data via x402. No account. Fixed USDC price. MCP-ready.

## Output

Returns a structured JSON object with the identified Incoterm rule and year, named place, seller obligations, buyer obligations, risk transfer description, duty availability status, a list of findings (extracted facts and missing fields), compliance status, and a list of limitations clarifying what the analysis does and does not cover (e.g. no duty calculation, no customs filing).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "file": {
   "type": "object",
   "required": [
    "mediaType",
    "fileBase64"
   ],
   "properties": {
    "filename": {
     "type": "string",
     "maxLength": 180,
     "minLength": 1
    },
    "mediaType": {
     "enum": [
      "application/pdf",
      "text/plain"
     ],
     "type": "string"
    },
    "fileBase64": {
     "type": "string",
     "maxLength": 12000000,
     "minLength": 1
    }
   },
   "additionalProperties": false
  },
  "text": {
   "type": "string",
   "maxLength": 200000,
   "minLength": 1
  },
  "incoterm": {
   "type": "string",
   "maxLength": 80,
   "minLength": 3
  },
  "namedPlace": {
   "type": "string",
   "maxLength": 160,
   "minLength": 1
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "duty": "unavailable",
  "risk": "Passes when the goods are on board the vessel.",
  "buyer": "Handles the main carriage and import after loading.",
  "seller": "Delivers the goods on board the vessel at the named port.",
  "status": "incomplete",
  "findings": [
   {
    "code": "incoterm_named",
    "kind": "extracted",
    "detail": "FOB was read as a named Incoterms rule. This is not a customs ruling."
   },
   {
    "code": "incoterm_year_missing",
    "kind": "missing",
    "detail": "No Incoterms year was printed. 2010 and 2020 were not assumed."
   }
  ],
  "incoterm": "FOB",
  "checkedAt": "2026-11-02T19:00:00.000Z",
  "namedPlace": "Felixstowe",
  "limitations": [
   "No customs declaration was submitted and no shipment was booked.",
   "Duty rates, restrictions, sanctions status, and country-specific requirements are not invented.",
   "An HS code candidate is not a customs classification.",
   "Only the documents and shipment fields in this request are compared.",
   "The obligation text is the named Incoterms rule. It is not a filing instruction or a duty calculation."
  ],
  "incotermYear": "",
  "shipmentBooked": false,
  "declarationSubmitted": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-incoterms-obligation-extractor-577417f7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.brainiac.software](https://www.zero.xyz/host/www.brainiac.software/llms.txt)
