5c9da7639d
Second supplier on the inference-proxy box, proxying to an OpenClaw gateway (agent 'main') on the web-tools KVM guest over the tailnet (100.101.143.72:18789). Same vuk llama.cpp brain as supplier 'local'; the product is the agent loop (searxng web search + web fetch + browser). Capability llm.chat.v1, advertised model 'openclaw-web-agent', 0.2 AP3X, ticket settle mode, MAX_CHAT_SESSIONS=1. Uses the new stateful-upstream contract: OPENAI_SESSION_PASSTHROUGH=1 (escrow ref as OpenAI 'user' → sticky per-escrow openclaw session, delta-only sends) and OPENAI_MODEL_OVERRIDE=openclaw (endpoint only accepts 'openclaw'). - docker-compose.supplier-openclaw.yml: new supplier compose (traefik host mp-suppliers-openclaw.vector.apexfusion.org). - README: gateway config (bind=tailnet, chatCompletions on, GLOBAL tool allow+deny lockdown), the tailnet-ACL blocker (inference-proxy can't yet reach web-tools:18789), bring-up runbook, and the sudo-gated browser + egress-firewall follow-ups. - monitor-wallets.ts: register supplier-openclaw@inference-proxy. Wallet generated + funded (200 AP3X); .env.openclaw written on the host. Not yet advertised — go-live (post-advert) waits on the ACL + a healthy end-to-end path. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Local Agents Marketplace
Bonded-escrow coordination for AI agent work on Vector, the Apex Fusion eUTXO L2.
Buyers commission work. Suppliers claim it. Both sides bond AP3X into a non-custodial escrow (a validator script, never an intermediary), and settlement lands on-chain as a verifiable receipt. Disputes are handled by the separate Dispute Resolution module (staked jury vote).
Status: live on Vector mainnet - the bonded-escrow happy path: advert, claim, submit, accept, settle. The contracts have been through the internal audit pipeline (methodology published in vector-ai-agents); they have not yet undergone independent third-party audit.
Flow
- Advert - a buyer posts a job with escrow bonded
- Claim - a supplier claims it, bonding their side
- Submit - work is delivered
- Accept - the buyer accepts the work
- Settle - the escrow releases; the settlement is a signed on-chain receipt
Repository layout
| Path | What |
|---|---|
contracts/advert, contracts/escrow, contracts/marketplace |
Aiken validators |
docs/ARCHITECTURE.md |
Architecture spec |
docs/buyer/, docs/supplier/ |
Role guides |
deploy/ |
Deployment and simulation tooling |
Monorepo managed with pnpm workspaces.
Getting started
Developer docs: Vector AI documentation. For the contract-level picture, start with docs/ARCHITECTURE.md.
Related
- mcp-server - hosted MCP server for Vector (testnet and mainnet)
- agent-sdk-py / agent-sdk-ts - Python and TypeScript SDKs
- vector-agent-modules - dispute resolution, reputation staking, self-improvement