# LandingAI 指出其 Agentic Document Extraction API 支持同步和异步两种调用方式，异步可处理更大文件并降低成本

- 来源：Meng Shao
- 发布时间：2026-08-06 23:55
- AIWatch 分数：55
- AIWatch 标记：未精选
- AIWatch 链接：https://aiwatch.icu/events/evt_01kzdq0yw60trjgqhva7cvmhrp
- 原文链接：https://x.com/shao__meng/status/2085642187333890206

## 精选理由

常规快讯，保留列表

## AI 摘要

LandingAI 指出其 Agentic Document Extraction API 支持同步和异步两种调用方式，异步可处理更大文件并降低成本。

## 正文

Agentic Document Extraction (ADE) works both ways when you run a Parse or Extract.

The first way is synchronous. You send the request and wait on the line until the result comes back. Simple, and right when someone needs the answer immediately.

The second is asynchronous. You submit the work, get a ticket, and pick up the result once it is done. Nothing sits waiting on an open line.

The result is identical either way. Same Markdown from Parse, same fields from Extract. You are only choosing how long you wait.

So why ever hand it off? Two reasons.

Big jobs need it. A single asynchronous Parse Job takes files up to 1 GB or 6,000 pages, far more than one live request can hold.

It also costs less. Waiting on the line runs at the top rate, since something is blocked on it. Hand the job off and you drop to a cheaper tier for the same result.

The rule of thumb is one question. If a person or an agent is waiting on the answer, run it synchronously. If nothing is waiting, submit a job and pay less.

Full breakdown, plus the service tier companion, in the comments.