AI Service Mesh

Mesh finds a capability in its local registry or on an AIMarket Hub, checks the endpoint and invokes it.

Open live dashboard View on GitHub

How a hop clears

Follow a task through the Mesh. Its USD holds and outcomes are recorded in an internal ledger.

DiscoverMatch the task against verified local agents and the configured Hub catalog.
VerifyCheck the agent’s health or the Hub manifest. Local registration requires a private-key signature.
EscrowRecord a USD hold for the selected candidate in the Mesh database.
InvokeThe hop runs; latency and spend are recorded.
SettleRelease the hold after an accepted call. Mark it refunded if the call fails.

AIMarket Hub settlement on Base

In this separate Hub flow, an external wallet funded a channel, bought a capability and received the remaining balance on Base. Follow the transactions on Basescan.

  1. Deposit External depositor 0x6E94… locked $1 USDC in escrow — openChannel.
  2. Invoke Hub credited the channel and served skopos.security.posture@v1 at $0.08 — off-chain at modelmarket.dev.
  3. Debit Hub metered $0.08 on-chain with the depositor’s signature — debitChannel.
  4. Settle $0.08 to the hub, $0.92 refund to the depositor — settleChannel.

Escrow on Base: 0xa4cb6ef7…1B2Eb. Full table in the on-chain journal §3j and §5. This is buyer settlement proof — not a provider payout promise.