File parsing is a AI tools block from Orvain UI, built for React and Vue with a matching Figma frame.
Best for
Reading a document into fields and sending them where they go
Anatomy
Drop or pick a file · the page with each field's spot marked · fields filling as they are read · a choice where the page is unclear · add to the destination, with a receipt
The assistant reads it and fills in the fields. Nothing is saved until you add it.
In the Orvain Library
Get File parsing for your product
The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.
Part of AI tools
05parts
The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.
900 px
Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.
Where AI tools earns its place
Reach for AI tools
Reach for something else
06to keep
What the block ships with. Hold on to these as you make it yours.
1 line
Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.
Add the Orvain “File parsing” block to this page: drop or pick a file, the page with each field's spot marked, fields filling as they are read, a choice where the page is unclear, add to the destination, with a receipt.
File parsing is a AI tools block from Orvain UI, built for React and Vue with a matching Figma frame. Best for reading a document into fields and sending them where they go.
5 parts: drop or pick a file; the page with each field's spot marked; fields filling as they are read; a choice where the page is unclear; and add to the destination, with a receipt. Keep them all, or drop the ones your product does not need; the rest of the block holds together without them.
Yes. It is drawn at 900px and never stretched past that. Below it, its controls, text and spacing step down with the container the block sits in rather than the browser window, so it holds up in a sidebar, a tablet layout and a 390px phone without clipping or sideways scrolling.
It ships with text labels on every icon-only button, full keyboard reach with a visible focus ring, states that never rely on colour alone, text contrast that holds when you retheme it, no animation for visitors who ask for reduced motion, and click targets of at least 24px.
It is part of every Orvain Library plan: the React and Vue code, its frame in the Orvain Figma file, and the Orvain MCP server. With the MCP connected, an AI assistant such as Claude Code, Cursor or v0 can build it from one line: “Add the Orvain File parsing block to this page.”
A plain conversation with no tools or sources. The assistant thread in the AI Chat family is lighter and says everything there is.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
File parsing is a AI tools block from Orvain UI, built for React and Vue with a matching Figma frame.
Best for
Reading a document into fields and sending them where they go
Anatomy
Drop or pick a file · the page with each field's spot marked · fields filling as they are read · a choice where the page is unclear · add to the destination, with a receipt
The assistant reads it and fills in the fields. Nothing is saved until you add it.
In the Orvain Library
Get File parsing for your product
The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.
Part of AI tools
05parts
The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.
900 px
Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.
Where AI tools earns its place
Reach for AI tools
Reach for something else
06to keep
What the block ships with. Hold on to these as you make it yours.
1 line
Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.
Add the Orvain “File parsing” block to this page: drop or pick a file, the page with each field's spot marked, fields filling as they are read, a choice where the page is unclear, add to the destination, with a receipt.
File parsing is a AI tools block from Orvain UI, built for React and Vue with a matching Figma frame. Best for reading a document into fields and sending them where they go.
5 parts: drop or pick a file; the page with each field's spot marked; fields filling as they are read; a choice where the page is unclear; and add to the destination, with a receipt. Keep them all, or drop the ones your product does not need; the rest of the block holds together without them.
Yes. It is drawn at 900px and never stretched past that. Below it, its controls, text and spacing step down with the container the block sits in rather than the browser window, so it holds up in a sidebar, a tablet layout and a 390px phone without clipping or sideways scrolling.
It ships with text labels on every icon-only button, full keyboard reach with a visible focus ring, states that never rely on colour alone, text contrast that holds when you retheme it, no animation for visitors who ask for reduced motion, and click targets of at least 24px.
It is part of every Orvain Library plan: the React and Vue code, its frame in the Orvain Figma file, and the Orvain MCP server. With the MCP connected, an AI assistant such as Claude Code, Cursor or v0 can build it from one line: “Add the Orvain File parsing block to this page.”
A plain conversation with no tools or sources. The assistant thread in the AI Chat family is lighter and says everything there is.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Describe it below, or start from a suggestion. Every section lands here as it is built, and you can point at anything to change it.
/to writeCtrl↵to buildYou asked: Customers get two receipts when Stripe retries a payment webhook. Can you fix it?
Nearly full
Nearly full. About 10 turns before I summarise older ones.
Describe it below, or start from a suggestion. Every section lands here as it is built, and you can point at anything to change it.
/to writeCtrl↵to buildYou asked: Customers get two receipts when Stripe retries a payment webhook. Can you fix it?
Nearly full
Nearly full. About 10 turns before I summarise older ones.