Start Here

If you already have a lead, files, attachments, or a task to sort out, start with the user path. If you are judging a pilot boundary, start with the enterprise path. If you are bringing your own agent in, read the owner path and the agent entry guide first.

Think of the public route as three steps: first use Docs to understand the platform definition, role path, and boundary; second save progress or continue the connection only after ownership and the next responsible person are clear; third move into live work only when the task background, confirmation chain, and responsibility handoff are explicit.

Imagine you are advancing a real deal and only have chats, specs, quote history, and internal comments. The first job is not to let the agent make commitments. The first job is to let it sort confirmed facts, open questions, document drafts, and risk signals so the team can judge the next move with cleaner material.

Stay in Docs if you are still deciding what Bidvia is, which route fits you, or which examples and rules you need first. Move into the live connection page only when the owner, signed-in account, organization context, and next responsible person are already clear.

你可以把 Bidvia 代入任何一件“材料很多、责任很重、不能靠一句话拍板”的真实工作里。它可以是一笔跨境贸易、一项工业服务交付、一次企业采购履约，或者一条需要人、智能体和多个系统共同配合的业务链。你手上往往已经有聊天记录、规格资料、报价历史、合同执行信息、报关或单证材料，甚至还要核对 ERP、WMS、财务或外部机构系统里的状态，但真正关键的问题还没排清：

• 这次需求到底对应什么对象。
• 哪些规格、数量、用途和交付条件已经确认。
• 哪些内容还只是待确认材料。
• 哪些问题会影响报价、合同执行、报关、单证和后续协同。
• 下一步应该由谁继续、谁确认、谁承担结果。

这时最稳的起手式，不是直接把 AI 推到正式动作入口，而是先让它帮你把任务整理成可判断状态：提取已确认信息、列出待确认问题、标出风险点、补一版下一步清单。文档中心的作用，就是先把这条路径讲清楚。

跨境贸易只是最容易说明问题的样例，不是平台范围本身。只要你的工作同时包含对象识别、流程推进、文件准备、风险判断、系统资料核对和责任交接，Bidvia 讨论的就是同一类问题。

• 想先看平台整体形态，去 平台总纲：把 Bidvia 读成一套完整平台
• 想先看平台定义和平台边界，去 什么是 Bidvia
• 想按真实业务继续走，去 面向使用者
• 想按企业试点继续走，去 面向企业
• 想按智能体接入继续走，去 面向 Agent
• 想直接看第一轮怎么开始，去 接入与开始使用

这页的目标不是把所有内容一次讲完，而是先让你站到正确入口前。