正在加载视频...

视频加载失败

Introducing NDI 1.0 - a small model for document processing. #1 on Parse Index Normalized (across 6 public benchmarks) GPT-6 Astra performance at 1/10th the cost 📈 Trained on 15M+ financial files for industry-grade accuracy. Get started with $25 in free credits: Reply "NDI" for a single file setup...

1,304,753 次观看 • 10 天前 •via X (Twitter)

43 条评论

Nace AI 的头像
Nace AI10 天前

OmniDocBench

Nace AI 的头像
Nace AI10 天前

ParseBench

Nace AI 的头像
Nace AI10 天前

MDPBench

Nace AI 的头像
Nace AI10 天前

ExtractBench

Kaitee 的头像
Kaitee10 天前

curious how it handles multi-page contracts with tables that span pages. most of these tools still choke on that.

Nace AI 的头像
Nace AI9 天前

Developer Access:

Nace AI 的头像
Nace AI9 天前

Developer Console Access

Veles 的头像
Veles10 天前

Already running drex in night desk, NDI for filings is the obvious add

kai. 的头像
kai.10 天前

1/10th the cost for financial doc parsing is massive.. specialized small models keep winning

carpe 的头像
carpe10 天前

how accurate is NDI on messy real invoices?

Ruuj 的头像
Ruuj10 天前

Making it cost efficient with such great results is a good one guys

Nawi 的头像
Nawi10 天前

The "every value links back to its source" part is the real flex. An agent you can audit beats an agent you have to trust.

ben. 的头像
ben.10 天前

bangerrr!!

marcus 的头像
marcus10 天前

love that you shipped a single file setup for Claude Code and Codex. how long does it take to get parsing from zero?

Nace AI 的头像
Nace AI10 天前

Pretty much right away, add your API key, and you can start parsing in a few minutes.

YasuoXBT🥷 的头像
YasuoXBT🥷9 天前

Ndi

Nace AI 的头像
Nace AI9 天前

check your DMs!

Arman Suleimenov 的头像
Arman Suleimenov9 天前

NDI

Nace AI 的头像
Nace AI9 天前

Check your DMs!

Kaif 的头像
Kaif10 天前

"astra performance at 1/10th the price" is the only benchmark founders actually read

lis 的头像
lis10 天前

trying this

LX™ 的头像
LX™10 天前

Parse, split, classify, extract, ground. One document goes through all five and stays linked to its source.

CesarAG 的头像
CesarAG10 天前

I'll try it, it will help me a lot in my work

zen. 的头像
zen.10 天前

curious how much the 15M+ financial files bias it toward finance. does accuracy hold up on contracts or medical docs?

Abdirakhman Ismail 的头像
Abdirakhman Ismail10 天前

NDI

Nace AI 的头像
Nace AI10 天前

Your DMs are closed, DM us and we’ll send it over!

Alex Ai | Tools & Updates 的头像
Alex Ai | Tools & Updates9 天前

GPT-6 level accuracy at tenth cost on financial docs impressive

banzaan 的头像
banzaan10 天前

@pouyanroohii

Mour₳‎ 的头像
Mour₳‎10 天前

Ndi

Nace AI 的头像
Nace AI10 天前

Your DMs are closed, DM us and we’ll send it over!

Mira Synth Tech 的头像
Mira Synth Tech10 天前

Hitting number one on the Parse Index with that kind of cost efficiency is seriously impressive

Clara AI 的头像
Clara AI10 天前

Affordable, high-accuracy document processing could be a game changer for AI workflows

Ace 的头像
Ace10 天前

Everyone's building smarter agents, but half of them are still squinting at blurry PDFs. Fixing the eyes first makes a lot of sense.

Lau R🍕 的头像
Lau R🍕10 天前

the mountain in that image is doing more marketing than the entire product page

NOOR TECH 的头像
NOOR TECH8 天前

Outstanding Nace AI launch, NDI 1.0 delivers top accuracy at a fraction of cost efficiently!

LastResort 的头像
LastResort9 天前

Cost per page? @grok

AM 的头像
AM10 天前

NDI

Nace AI 的头像
Nace AI10 天前

Check your DMs 🙌

Zivlen 지능 的头像
Zivlen 지능10 天前

interested

An Nayal 的头像
An Nayal8 天前

1/10th the cost.. you're cracked 🫡

Ye Cooper 的头像
Ye Cooper10 天前

NDI

Nace AI 的头像
Nace AI10 天前

Check your DMs!

Aaliya 的头像
Aaliya10 天前

15M files is a lot of data to train on

相关视频

Official OpenAI tip for Codex: stop burning GPT-6.1 Sol context on tasks GPT-6 Luna can swarm, while GPT-6 Astra sits idle put Astra on call as a dedicated adversary codex --model gpt-6.1-sol --agent adversary GPT-6.1 Sol acts as the lead architect, scoping architecture and validating pull requests GPT-6 Luna teammates take isolated git worktrees and hammer out implementations at medium effort GPT-6 Astra monitors the peer-to-peer bus as a dedicated adversary, only stepping in at three critical moments: → before a contract locks: does the frontend payload match the backend schema? → when a test breaks twice: are we patching the bug or just hiding the symptom? → before calling done: what attack surface or edge case did everyone overlook? GPT-6 Luna builds. GPT-6 Astra challenges. GPT-6.1 Sol merges and ships Jev engineering runs the identical pattern one layer down: mechanical decisions that need no reasoning (which file to open, which tool to invoke, retry or abort) execute in 16ms, so the frontier models only wake up when execution paths actually diverge Plan on high. Delegate on medium. Keep the adversary on peer-to-peer call. - the full team setup > GPT-6.1 Sol on high coordinates the session and synthesizes PRs > teammate-ux builds client state inside a separate git worktree > teammate-back writes endpoints and handles Redis atomic locks > teammate-adv runs invariant fuzzing and catches replay vulnerabilities > all teammates communicate directly over peer-to-peer messaging without coordinator drag > tasks.json manages file-level mutex locks so nobody steps on another worktree paste the setup and this prompt into Codex CLI below: "Configure my Codex workspace for autonomous agent teams: 1. Audit ~/.codex/agents and .codex/agents for teammate profiles fitting ux, backend, and adversary > Generate definitions only for missing roles > Pin model: gpt-6-luna, model_reasoning_effort: medium for workers, and model: gpt-6-astra for adversary > Assign each worker an isolated git worktree branch to eliminate file conflicts 2. Enable agent teams in ~/.codex/config.toml: > Set [agents] max_concurrent_threads_per_session = 8 > Lock main session model to gpt-6.1-sol with model_reasoning_effort = 'high' > Set approvals_reviewer = 'auto_review' 3. Initialize tasks.json in repo root with atomic file locking, allowing teammates to claim subtasks and resolve contracts directly over inter-agent messaging without coordinator intervention 4. Add a team rule to AGENTS.md: teammates must request an adversary security review before opening a pull request for the lead session Show every configuration diff first. Do not apply edits until confirmed" ↳

mirku

31,072 次观看 • 16 天前