01 / Identity
Know the counterparty first
Bind a supplier account, version, signing key, endpoint, and payout. Registration alone never makes a service trusted.
NEAR testnet payments verified · refund-gap proof pending
Give an agent a spending limit and a list of permitted suppliers. AgentTrust checks signed invoices, capability evidence, and owner rules before reserving native NEAR for payment.
Native development kit
From a prepared checkout, run the pure checks. The runtime runbook separates compiled code from observed native receipts.
Illustrative flow — not a recorded transaction
request invoice CSV + stable payment ID
quote supplier-signed exact request
admission owner policy + capability checks
dispatch reserve → native NEAR transfer
settlement wait for final payment state
output check the returned audit report
01 / Identity
Bind a supplier account, version, signing key, endpoint, and payout. Registration alone never makes a service trusted.
01 / Identity
Bind a supplier account, version, signing key, endpoint, and payout. Registration alone never makes a service trusted.
Read Trust Model02 / Policy
Purchase and daily caps, explicit trust, blocks, pause, and a fixed dispatch rate are enforced before the core reserves funds.
View Payment Gate03 / Settlement
Follow each stable payment ID through pending, settled, or failed. A missing callback keeps the reservation; a timeout never authorizes a second payment.
Inspect SettlementOne native NEAR core · deployed on testnet
A single Rust contract owns the registry, policy admission, and payment ledger. A transfer and its callback run in separate receipts; pending never means paid.
Direct owner controls: trusted services, blocks, purchase caps, daily caps, pause, and restricted sessions.
Source moduleowner.rsReserve before dispatch, bind the exact invoice, and finalize once from a private callback.
Source modulepayments.rsVersioned supplier identity and issuer credentials scoped to one capability and conformance suite.
Source moduleregistry.rs/ Unparalleled performance
Supplier identity, owner limits, and capability evidence gate dispatch. Native receipts track settlement. The chart is decorative; no performance benchmark is claimed.
A local agent should ask for a service, not raw signing power. The six-tool local MCP keeps owner management separate and accepts a stable payment ID for every purchase.
The buyer selects from explicitly configured suppliers. Owner policy determines who may be paid and how much. An endpoint in the catalog is not permission to spend.
The buyer selects from explicitly configured suppliers. Owner policy determines who may be paid and how much. An endpoint in the catalog is not permission to spend.
An agent can choose the next useful service.Its owner decides the spending boundary.
AgentTrust connects the steps with reservations on NEAR.
Check beforedispatch.