Skip to main content
Glama

Arbitova

Base 链上非托管 USDC 托管 + AI 仲裁,用于代理间支付。

两个代理将 USDC 锁定在合约中,一方交付,另一方确认或提出争议,由中立的 AI 仲裁员进行裁决。Arbitova 从不持有资金——资金由合约持有。

无需 API 密钥。无需注册。无需托管。你的以太坊地址就是你的身份。


为什么存在这个项目

目前市面上所有的 A2A / 代理商业规范(MCP、Google 的 A2A、ERC-7683、Coinbase 的 Agent Commerce)都定义了代理如何沟通。但没有一个定义了当代理互不信任时资金如何流动。

Arbitova 是缺失的结算原语:

  • 确定性状态机。 createEscrow → markDelivered → {confirmDelivery | dispute → resolve | cancel}。没有隐藏分支,没有管理员覆盖。

  • 超时后不自动释放。 审查窗口过期后会进入 DISPUTED 状态,而不是自动支付给卖家。沉默比错误的确认更安全。

  • 内容哈希链上固定。 卖家在买家检查后无法更换交付文件。

  • 逐案裁决透明度。 每一项仲裁员决定都是一个签名的 JSON blob;其 keccak256 存储在链上。完整的裁决历史记录可在 /verdicts 查询——无需聚合,无延迟。

这不是一个市场。没有 Arbitova 账户,没有上架费,没有专业版。协议本身就是全部产品。


Related MCP server: idios

快速入门 — Node.js SDK

npm install @arbitova/sdk ethers
import { Arbitova } from '@arbitova/sdk';

const buyer = await Arbitova.fromPrivateKey({ privateKey: process.env.BUYER_PK });

const { escrowId, txHash } = await buyer.createEscrow({
  seller: process.env.SELLER_ADDRESS,
  amount: '5.00',
  deliveryHours: 24,
  reviewHours: 24,
  verificationURI: 'https://example.com/spec.json',
});

console.log(`Escrow #${escrowId} locked — ${buyer.explorerTx(txHash)}`);

卖家端、仲裁员端、浏览器钱包集成:请参阅 packages/sdk-js/README.md。

快速入门 — Python SDK

pip install "arbitova[path_b]"
from arbitova import path_b

result = path_b.arbitova_create_escrow(
    seller="0x...",
    amount=5.00,
    verification_uri="https://example.com/spec.json",
)
print(result)

快速入门 — Claude / 任何 MCP 客户端

{
  "mcpServers": {
    "arbitova": {
      "command": "npx",
      "args": ["-y", "@arbitova/mcp-server"],
      "env": {
        "ARBITOVA_RPC_URL": "https://sepolia.base.org",
        "ARBITOVA_ESCROW_ADDRESS": "0xA8a031bcaD2f840b451c19db8e43CEAF86a088fC",
        "ARBITOVA_USDC_ADDRESS": "0x036CbD53842c5426634e7929541eC2318f3dCF7e",
        "ARBITOVA_AGENT_PRIVATE_KEY": "0x..."
      }
    }
  }
}

六个工具:arbitova_create_escrow、arbitova_mark_delivered、arbitova_confirm_delivery、arbitova_dispute、arbitova_cancel_if_not_delivered、arbitova_get_escrow。全部通过 ethers v6 在本地签名。你的私钥永远不会离开进程。

省略 ARBITOVA_AGENT_PRIVATE_KEY 可进入只读内省模式(适用于可观测性)。


生命周期

                      ┌──────────────────┐
                      │     CREATED      │ buyer locked USDC
                      └────────┬─────────┘
                               │
                               ▼ seller.markDelivered()
                      ┌──────────────────┐
                      │    DELIVERED     │ deliveryHash on-chain
                      └────────┬─────────┘
                               │
        buyer.confirmDelivery()│        │ buyer.dispute()
                               │        │ or seller.dispute()
                               ▼        ▼
                   ┌─────────────┐  ┌──────────┐
                   │  RELEASED   │  │ DISPUTED │ waiting for arbiter
                   └─────────────┘  └────┬─────┘
                                         │ arbiter.resolve(bps split + verdictHash)
                                         ▼
                                   ┌──────────┐
                                   │ RESOLVED │
                                   └──────────┘

未绘制的两个终端状态:CANCELLED(买家在交付窗口后调用 cancelIfNotDelivered)以及如果审查窗口在没有确认的情况下过期,则自动升级为 DISPUTED。


框架参考代理

在 Base Sepolia 上带有实时 AI 仲裁员的三个端到端 A2A 演示:

每个演示都通过真实的链上交易运行完整的 CREATED → DELIVERED → CONFIRMED(或 DISPUTED → RESOLVED)流程。


软件包

软件包

用途

@arbitova/sdk

Node.js / 浏览器 SDK (ethers v6)

arbitova

Python SDK,安装时使用 [path_b] 额外参数以支持链上功能

@arbitova/mcp-server

用于 Claude Desktop、Claude Code 或任何 MCP 客户端的 MCP 服务器(6 个链上工具)

每个软件包都提供相同的六个入口点,因此使用 Python SDK 的代理可以与使用 MCP 服务器的代理进行结算——它们访问的是同一个合约。


费用

时间

费用

支付方

confirmDelivery / 审查窗口过期自动结算

0.5%

从卖家收益中扣除

仲裁员解决争议

2%

按仲裁员裁决分配

费用在合约中累积。协议依靠这些费用运行;没有订阅费。


网络

网络

状态

合约

Base Sepolia

实时,真实的 Circle USDC

0xA8a031bcaD2f840b451c19db8e43CEAF86a088fC

Base 主网

等待审计 + 多签仲裁员

待定

关注 开发日志 获取主网上线信息。


旧版本(路径 A)

v2.x 的 SDK 和 v3.4.0 的 MCP 服务器是针对 api.arbitova.com 的托管 HTTP 客户端。该架构存在四个结构性问题(数据库与链上数据漂移、托管钱包 Gas、单一 ADMIN_KEY、单一 WALLET_ENCRYPTION_KEY 单点故障),现已弃用,转而采用路径 B——即上述非托管链上设计。

旧软件包仍保留在 npm/PyPI 上,但已弃用。


许可证

MIT

Available Tools

7 tools
arbitova_cancel_if_not_deliveredA

Buyer cancels an escrow after the delivery deadline has passed and the seller has not marked delivery. Full USDC refund to buyer. Only callable by the buyer, only after deliveryDeadline has elapsed, and only when escrow is still in CREATED state. Call arbitova_get_escrow first to verify the deadline has passed and status is CREATED before calling this.

Inputs: escrowId (required).

arbitova_confirm_deliveryA

Confirm that the seller has delivered and the output meets ALL criteria in the escrow's verificationURI. ONLY call after you have: (1) fetched the delivery payload, (2) fetched and parsed the verificationURI criteria document, (3) compared the payload against EVERY criterion, (4) are fully confident every criterion is satisfied. If anything is missing, wrong, ambiguous, incomplete, or the seller did not deliver the agreed output — DO NOT call this. Call arbitova_dispute instead with a specific reason citing the failed criterion. Silence is safer than a wrong confirmation: if you do not confirm within the review window, funds auto-escalate to AI arbitration, which protects the buyer by independently evaluating delivery.

Inputs: escrowId (required).

arbitova_create_escrowA

Buyer locks USDC into the Arbitova EscrowV1 smart contract. Calls USDC.approve() then createEscrow() on-chain. Requires USDC balance >= amount. deliveryWindowHours = how long the seller has to deliver (default 24). reviewWindowHours = how long the buyer has to verify after delivery is marked (default 24). verificationURI must point to a publicly fetchable JSON document listing every criterion the delivery will be checked against. If the review window expires without confirmation or dispute, funds auto-escalate to arbitration. Silence protects the buyer — you do NOT need to confirm promptly.

Inputs: seller (required), amount (required), verificationURI (required), deliveryWindowHours, +1 more.

arbitova_disputeA

Open a dispute when delivery is missing, incorrect, incomplete, or violates the verification criteria. Disputes trigger AI arbitration which independently evaluates the delivery and can split funds fairly. Call this whenever arbitova_confirm_delivery feels uncertain — when in doubt, dispute. The reason field MUST cite specific criteria from verificationURI that were not met, e.g. "Delivery at [URI] is missing criterion 3: word count is 400 but spec requires >= 1000." Either the buyer OR the seller can open a dispute.

Inputs: escrowId (required), reason (required).

arbitova_escalate_if_expiredA

Permissionlessly escalate a DELIVERED escrow to DISPUTED after the review window has expired. Any address can call this — buyer, seller, or an independent watcher. Use when the buyer went silent past reviewDeadline: this unblocks the seller and routes the escrow into arbitration instead of leaving funds stuck. Only valid when status is DELIVERED and block.timestamp > reviewDeadline. Call arbitova_get_escrow first to verify status and deadline before calling this.

Inputs: escrowId (required).

arbitova_get_escrowA

Fetch the current on-chain state of an escrow: buyer, seller, amount, deadlines, status, verificationURI, and deliveryHash. Use this to check whether delivery has been marked before fetching the payload, and to verify the reviewDeadline before deciding to confirm or dispute. Status values: CREATED (awaiting delivery), DELIVERED (seller marked done, review window open), RELEASED (funds released to seller), DISPUTED (in arbitration), RESOLVED (arbiter resolved), CANCELLED.

Inputs: escrowId (required).

arbitova_mark_deliveredA

Called by the SELLER after completing the work and uploading the deliverable to a stable URL. deliveryPayloadURI must point to the completed, publicly fetchable deliverable — the contract hashes this URI on-chain. Do NOT call before work is actually done. Do NOT use a temporary or expiring URL. The arbiter will fetch this URI during dispute resolution — a broken or mismatched URL counts as non-delivery. Before calling: complete all work to spec, upload to a stable URL (IPFS or persistent storage), and verify the content matches every criterion in verificationURI.

Inputs: escrowId (required), deliveryPayloadURI (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a unique action in the escrow lifecycle (create, get, mark delivered, confirm, cancel, dispute, escalate). No two tools have overlapping purposes, and descriptions clarify exactly when each should be used.

    Naming Consistency5/5

    All tools follow the pattern 'arbitova_<verb>_<condition>', using snake_case consistently. The names are descriptive and predictable, making it easy to infer the tool's action from its name.

    Tool Count5/5

    7 tools is an ideal size for an escrow management server. Each tool serves a necessary function in the lifecycle without unnecessary redundancy or bloat.

    Completeness5/5

    The tool set covers the full escrow lifecycle: creation, status retrieval, delivery marking, confirmation/cancellation, dispute opening, and escalation. There are no obvious gaps that would hinder an agent from managing an escrow end-to-end.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Settlement rails for AI labor — USDC escrow on Base Mainnet, 1% protocol fee, designed for autonomous agents. 10 MCP tools covering the full escrow lifecycle: * Quoting calldata for create-intent, submit-proof, release-funds (broadcast gated) * Single-call x402 payment binding (replaces the 5-step x402 dance with one HMAC-signed POST) * Server-side reputation from on-chain event scan * Li
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Private escrow for AI agent work on Beam mainnet an agent locks payment, the worker locks collateral, and delivery settles on hash match or review, with M of N arbitrator voting and slashable worker bonds as the dispute backstop. 22 tools cover the full contract lifecycle, and dispute voting is deliberately not an agent tool, so an agent can never rule in its own favour.
      26
      MIT