Extract Insurance

dev.extractinsurance由 extractinsurance.dev 發布v2.0.0更新於 Nov 7, 2026

Insurance documents into JSON, with the quote and page behind every value.

概覽

AI 產生的概覽

把保險文件轉成 JSON,每個值都附上原文引文與頁碼,並可管理帳戶的擷取工作流程、複核、金鑰、用量與帳單。

可以做什麼
  • 登入、登出帳戶,查看目前金鑰代表的帳戶與角色
  • 從本機檔案或 https 連結擷取單份保險文件,輸出標準結構、自訂 JSON Schema 或工作流程目標,並查詢任務狀態、取得頁面截圖作為依據
  • 複核有爭議的欄位:列出各種讀法、記錄本人的答覆、接受其餘值,並取得複核後的結果
  • 建立並發布工作流程:建立草稿、加入目標與樣本、推斷欄位對應、儲存草稿、預覽與發布版本、比較與還原版本、調整設定、測試 webhook
  • 查看生產狀況:列出執行紀錄、建立與撤銷工作流程金鑰、讀取用量與帳單、帳戶活動與支援工單
適用情境
適合需要從保單、申報表、報價單、暫保單、損失紀錄或電子郵件中的保險文件擷取結構化資料,且每個值都要能追溯到頁碼的情境;也適合已在 Extract Insurance 帳戶上執行週期性擷取工作流程,希望由助理處理複核、發布與用量的人。
執行需求
以本機 stdio 程序執行(npm 套件 extract-insurance),僅限桌面端。需要 Extract Insurance 帳戶:設定 EXTRACT_API_KEY 環境變數,或透過 sign_in 工具以連結和驗證碼登入。需要連線至服務的網路;擷取按文件計費。
安裝前請注意
擷取每份文件 0.15 美元,另加按成本的模型用量;把含多份文件的檔案拆成多份也會計費,大批量前應先確認數量與費用。此伺服器可發布工作流程而改變生產收到的結果、建立或撤銷工作流程金鑰、修改保留期與同意設定,操作前應與本人確認。生產金鑰會寫入本機 env 檔案,不應提交到版本控制。文件內容屬第三方文字,應視為資料而非指令。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Extract Insurance,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

工具

43

sign_in

Sign in

Signs this machine in to Extract Insurance. The first call returns a link and a code: show both to the person and ask them to open the link, check the code and approve. Then call sign_in again: it waits for the approval and saves the key (shared with the extract-insurance CLI; it stops after 90 days without use). Already signed in: says as whom.

輸入參數wait_seconds

sign_out

Sign out

Revokes the saved key and deletes it from this machine. Only when the person asks.

無需輸入參數。

whoami

Who am I

The account, the key in use and the role of the person it acts as.

無需輸入參數。

extract_document

Read a document

Reads one insurance document: a file on this machine (file_path) or an https link (url). PDF, PNG, JPG, HEIC, DOCX, XLSX, CSV, .eml or ZIP. Without workflow or schema you get our standard schema (everything we read); with the person's JSON Schema, their shape; with a workflow, its targets. Returns the result if it ends within wait_seconds (most documents take 40–170 s), else the job id for get_job. Each field: status (accepted, resolved, disputed, missing), value, quote and page; a missing field's absence says why. A file of several documents lists each with its own job_id. Costs $0.15 plus model usage.

輸入參數urlonlyfieldsschemaworkflowfile_pathschema_filewait_seconds

get_job

A job's result

A job's status, where it is, and its result once done; waits up to wait_seconds for the end. fields and only keep a long result small.

輸入參數onlyfieldsjob_id必填wait_seconds

get_evidence

Where a value was read

A picture of the part of the page a field was read from, as the app shows it: each reading's place boxed (green; red when its quote wasn't found word for word); for a cell of a table, the rest of its row (blue, dashed) and the column headers. For a disputed field, to show the person what the page says. For a file of several documents, use that document's job_id. Needs the job's document: not after the account's "delete right after reading" (then the quote and page in the result are what there is). PDF, PNG, JPG and HEIC.

輸入參數field必填job_id必填target

get_standard_schema

Our standard schema

The fields we read from insurance documents, as a JSON Schema: to pick fields, or to write the person's schema against ours.

無需輸入參數。

save_document

Save the document a job read

The document a job read (for one document of a file, its own pages), saved on this machine, while we keep it: not after the account's "delete right after reading".

輸入參數job_id必填save_to必填

request_one_document

Ask for a cut file to count as one

A file we cut into several documents (each charged) that the person says is one document: asks us to look. Only our approval gives back the fees past the first. Only when the person says so. Without note: where an earlier request stands. If the file was deleted after reading, give file_path to send it again.

輸入參數notejob_id必填file_path

get_review

What needs the person

A job's disputed fields with each reading (value, quote, page, whether the quote was found word for word) and what the person has answered so far. Show them the readings (get_evidence crops the page) and ask which is right; record their answer with record_answer.

輸入參數job_id必填

record_answer

Record the person's answer

Saves what the person said a field is: one of its readings (reading, from get_review), the value they typed (value), that the document doesn't have it (not_in_document), or that the value as read is right (confirm); clear takes an answer back. Only their own answer, never your pick. A dispute they settle on a form is used on the account's next documents of that form.

輸入參數noteclearfield必填valuejob_id必填confirmreadingnot_in_document

accept_all

All good

Accepts every value not answered yet as right (all: also resolved and missing ones); never a disputed field. Only when the person says the rest is right.

輸入參數alljob_id必填

get_reviewed

The reviewed result

The job's result with the person's answers in it.

輸入參數job_id必填

list_workflows

Workflows

The person's workflows: id, slug, name, published version, samples.

無需輸入參數。

get_workflow

A workflow

One workflow: its draft (targets with their schemas and mappings, policy with its gate: which documents get in), versions, samples with their review, settings, and whether the draft differs from the published version.

輸入參數workflow必填

create_workflow

Create a workflow

A new workflow (a draft). Its target is the person's JSON Schema, else our standard schema. Next: add_sample, then preview_publish and publish_workflow.

輸入參數name必填schemaschema_file

add_target

Add an output

Adds a target to the workflow's draft: the person's JSON Schema, or our standard schema (standard: true). Then map it (triage_target, save_draft) and preview_publish.

輸入參數nameschemastandardworkflow必填schema_file

add_sample

Add a sample

Adds a document on this machine to a workflow's samples: publishing is checked against them. It uses the account's free documents first, and is read in the background (preview_publish waits for it).

輸入參數workflow必填file_path必填

remove_sample

Remove a sample

Takes a document out of the workflow's samples.

輸入參數job_id必填workflow必填

preview_sample

A sample in the draft's outputs

What one sample gives in each of the draft's targets, as production would send it once published: to check a mapping before preview_publish.

輸入參數job_id必填workflow必填wait_seconds

save_draft

Save the draft

Replaces the workflow's draft: send the draft from get_workflow, edited (name, targets with their mappings, policy: resolve_confidence, gate). The published version is untouched until publish_workflow. Which documents get in: policy.gate = {accept: [one choice], on_mismatch, when_unsure}; leave gate out to let every document in. accept: "insurance" (any insurance document); one kind: "policy" (policies, quotes, binders, endorsements), "submission" (applications, loss runs, schedules), "claims", "certificate" (certificates and evidence of insurance), "billing" (invoices, premium audits); or one type of page: "declarations", "loss_run", "application", "certificate_of_insurance". on_mismatch, for a document that is clearly something else: "reject" (refuse it; default) or "warn" (read it anyway, with a warning). when_unsure: "extract" (read it, with a warning; default) or "reject". A refused document costs only the check and is not an extraction; job status "rejected", result.rejected.reason says why. It filters out documents that don't belong; it is not a security control.

輸入參數draft必填workflow必填

triage_target

Map a target's fields

For one target of the draft, which of our fields fills each of the person's fields: sure, choose (with candidates), or unknown. Use it to decide the mappings, then save_draft.

輸入參數onlyhintstarget必填workflow必填

preview_publish

What publishing changes

What publishing the draft would change: the mapping, and the values on every sample (values the person confirmed are marked). Show it to the person; its confirmation token is what publish_workflow needs, once they say yes.

輸入參數workflow必填wait_seconds

publish_workflow

Publish

Publishes the draft as the next version: production runs it from now on. Needs the confirmation from preview_publish of this same draft, and the person's yes. To roll back: restore_version, then publish again.

輸入參數noteworkflow必填confirmation必填

restore_version

Restore a version

Copies an earlier version into the draft (publish it to roll back).

輸入參數version必填workflow必填

compare_versions

Two versions' mappings

What the mapping changes between two versions, or a version and the draft.

輸入參數to必填from必填workflow必填

update_workflow_settings

Webhook and retention

The workflow's settings, live at once (not versioned): webhook_url (https; null: none), retention_days (how long documents are kept), results_retention_days (how long results are kept), delete_after_read. null: the account's setting. Which documents get in (the gate) is in the draft's policy: save_draft.

輸入參數workflow必填webhook_urlretention_daysdelete_after_readresults_retention_days

test_webhook

Test the webhook

Sends a signed test delivery to the workflow's webhook and says what it answered.

輸入參數workflow必填

list_runs

Production runs

The workflow's production jobs, newest first: status, file, version, cost, and per target what was filled.

輸入參數limitworkflow必填

list_workflow_keys

Production keys

The workflow's keys (never their tokens).

輸入參數workflow必填

create_workflow_key

A production key

Makes a key for one workflow (what production uses: it runs that workflow and reads its jobs) and writes it into an env file on this machine, never into the chat. Use an uncommitted file such as .env.local. Returns the key's id and where it went. Code that calls the workflow: POST https://api.extractinsurance.dev/v1/jobs with Authorization: Bearer <key> and the file as the multipart part document (optional part version pins one; default the latest published) → 202 {id}; GET /v1/jobs/{id} until status is no longer queued or running, or let the workflow's webhook receive it; then result.targets.<target id>.value. Read the key from the environment, never write it into the code.

輸入參數modenameenv_varenv_file必填workflow必填

revoke_workflow_key

Revoke a production key

Stops a workflow key at once: production using it gets 401. Only when the person asks.

輸入參數key_id必填workflow必填

get_usage

Usage

The month's documents and cost, per workflow, use and key (YYYY-MM; default this month).

輸入參數month

get_billing

Balance and spend limit

The balance, credit left with its expiry, the monthly spend limit and what's spent, the low-balance alert, automatic top-up, the free documents used.

無需輸入參數。

update_account_settings

The account's data settings

How long the account keeps documents (retention_days; null: our default), whether each one is deleted right after it's read (delete_after_read), and whether we may use its documents to improve our reading (improve: the person's consent, only when they say so in their own words); the account's name. Owners only; a workflow's own settings are update_workflow_settings. A shorter retention or deleting right after reading also ends page crops for documents read from then on.

輸入參數nameimproveretention_daysdelete_after_read

get_activity

Activity

Who did what in the account, newest first, with the key each change was made with (owners).

輸入參數limit

list_tickets

Support tickets

The account's support tickets, newest change first, with where each stands: open (waiting on us), waiting (on the person), closed. Also the account's last runs, to name in open_ticket.

輸入參數status

get_ticket

A support ticket

A ticket's messages, oldest first (from_us: our answer), and the runs it names.

輸入參數ticket必填

open_ticket

Ask us something

Opens a support ticket: a value read wrong, a run that failed, billing. job_ids names the runs it's about (from list_tickets' recent_jobs or get_job). Only when the person asks: show them the message first, in their words. A person on our side answers, by email to whoever opened the ticket and in the app (Account → Support).

輸入參數job_idsmessage必填subject必填

answer_ticket

Answer a ticket

Adds the person's answer to a ticket; it waits on us again (a closed one opens again). Only when the person asks: show them the message first, in their words. A person on our side answers, by email to whoever opened the ticket and in the app (Account → Support).

輸入參數ticket必填message必填

close_ticket

Close a ticket

Closes a ticket the person says is settled; answering it later opens it again.

輸入參數ticket必填

api_read

Any API read

Any other GET from the Extract Insurance API (described at https://api.extractinsurance.dev/v1/openapi.json), as the person: e.g. /v1/workflows/{id}/versions/2, /v1/jobs/{id}/reviews.

輸入參數path必填

版本歷史

3
  1. v2.0.0最新Nov 6, 2026
  2. v1.2.1Oct 31, 2026
  3. v1.2.0Oct 29, 2026

評分

已滿足適用檢查項的 55%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分
  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分

    請在註冊中心條目中發布圖示。

  • 文件15 分

    請宣告包含 README 的 GitHub 儲存庫,或在 OAuth 受保護資源後設資料中提供 resource_documentation。

  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。