Skip to content
Agent 介面

此網站不僅可讀,更可操作。

此類別中幾乎每個行銷網站都是代理必須截圖和猜測的牆。這個網站則不然,它提供了一個類型化的工具清單,通過瀏覽器中的WebMCP和其他地方的JSON-RPC。這是產品本身的主張,由行銷網站執行。

← Back to the agent directory

正在檢查

您的瀏覽器尚未發送navigator.modelContext。從2026年起大多數瀏覽器都沒有。相同的工具可透過/api/mcp上的JSON-RPC取得,它不需要任何瀏覽器支援。

  • list_bag_modules唯讀

    List every capability module AgentBag ships, each with a published status (live, beta, or bench) and the caveat that goes with it. Optionally filter by status. Use this first to understand what the product actually does.

    example: {"status":"bench"}

  • get_bag_module唯讀

    Fetch the full published entry for one module: what it does, why it matters, how it works, its status caveat, and its FAQs. Use after list_bag_modules when you need depth on a specific capability.

    example: {"slug":"trustgraph"}

  • search_bag唯讀

    Answer a natural-language question strictly from the published capability ledger, returning citations to the modules the answer came from. Declines rather than speculating when the ledger does not cover the question.

    example: {"question":"What stops one agent reading another agent data?"}

  • check_workspace_address唯讀

    Turn a proposed team name into the tenant subdomain it would become, and report whether that label is usable. Does not reveal whether an address is already taken; that is deliberate.

    example: {"name":"Acme Robotics"}

  • answer_faq唯讀

    Answer a common question about AgentBag in machine form: a terse declarative answer plus a flat object of primitive-valued facts you can assert against without parsing prose. Prefer this over search_bag for questions about pricing, limits, privacy, tenancy or how to evaluate the product. Call with no arguments to list every question.

    example: {"question":"what is not built yet"}

  • get_pricing_status唯讀

    Report the current pricing position honestly, including the fact that billing is deliberately disarmed and no numbers are published yet.

    example: {}

  • join_waitlist具副作用

    Submit an email address to the AgentBag waitlist, optionally reserving a workspace address. This sends data on the user behalf; confirm with them before calling it.

    example: {"email":"you@example.com","workspace":"acme"}

    無法在此處執行
端點

機器所需的一切。

從終端機試用

curl -s https://agentbag.ai/api/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

curl -s https://agentbag.ai/api/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call",
       "params":{"name":"list_bag_modules","arguments":{"status":"bench"}}}'
嵌入任何地方

只需一個 script 標籤,您的網站就擁有一個 Agent。

在任何頁面上加入一行 JavaScript。角落會出現一個品牌啟動器,訪客點擊後即可在沙盒化面板中與您發佈的 Agent 進行對話。無需管理 iframe、無需處理驗證、無需建置步驟。Agent 會讀取您的頁面、根據上下文回答,甚至可以在您啟用後與您的 UI 進行互動。

貼上至您的網站

<script
  src="https://agentbag.ai/embed.js"
  data-agent="<your-agent-folder-id>"
  data-accent="#5f6f3c"
  data-launcher="Chat with us"
  data-voice="on"
  data-page-context="on"
></script>

Shadow DOM 隔離

小工具在 Shadow DOM 根節點內渲染。您的 CSS 無法破壞它,它也不會破壞您的 CSS。在任何網站上皆能實現零樣式衝突。

沙盒化 iframe

對話面板在嚴格的沙盒中載入。無頂層導覽,無憑證洩漏。訪客 Token 會保留在框架內。您的主機頁面絕不會暴露。

延遲載入

在使用者點擊啟動器之前,不會建立 iframe。對您的頁面載入零影響。在有人真正想對話之前,不會有隱藏的網路請求。

設定

  • data-agent"<folder-id>"
    Your published agent folder ID. Required.
  • data-accent"#5f6f3c"
    Brand color for the launcher button and accents.
  • data-launcher"Chat with us"
    Custom text on the launcher pill. Up to 40 characters.
  • data-voice"on"
    Enable voice input. Users can speak instead of type.
  • data-position"left" | "right"
    Which corner the launcher appears in. Default: right.
  • data-theme"light" | "dark" | "auto"
    Color scheme for the chat panel.
  • data-page-context"on"
    Let the agent read visible page content to give contextual answers.
  • data-page-actions"on"
    Let the agent interact with the page: click, scroll, highlight elements.
  • data-context-selector"main"
    CSS selector scoping which content the agent can read. Default: main or article.

底層運作原理

  1. 1. 載入器在您的頁面中執行。 它會建立一個 Shadow DOM 主機並繪製啟動器按鈕。此時尚未建立 iframe,亦無網路開銷。
  2. 2. 使用者點擊啟動器。 建立 iframe 並帶有 sandbox 限制,並從我們的來源載入。訪客工作階段隨即開始。
  3. 3. 頁面上下文流入(選擇性啟用)。 如果 data-page-context="on", 載入器會從您的頁面中擷取可見文字,並將其傳送給 Agent 以提供上下文相關的回答。
  4. 4. 頁面動作驅動您的 UI(選擇性啟用)。 如果 data-page-actions="on", Agent 可以反白標示、捲動至並點擊您頁面上的元素,以引導使用者。