NEAR testnet payments verified · refund-gap proof pending

The trust layer for AI-agent payments on NEAR.

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

Inspect the payment boundary.

From a prepared checkout, run the pure checks. The runtime runbook separates compiled code from observed native receipts.

native-payment-flow · illustration

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

A clear boundaryfor agent spending.

Trust stack storytelling

01 / Identity

Know the counterparty first

Bind a supplier account, version, signing key, endpoint, and payout. Registration alone never makes a service trusted.

01 / Identity

Know the counterparty first

Bind a supplier account, version, signing key, endpoint, and payout. Registration alone never makes a service trusted.

Read Trust Model

02 / Policy

Put rules in the payment path

Purchase and daily caps, explicit trust, blocks, pause, and a fixed dispatch rate are enforced before the core reserves funds.

View Payment Gate

03 / Settlement

Keep uncertainty visible

Follow each stable payment ID through pending, settled, or failed. A missing callback keeps the reservation; a timeout never authorizes a second payment.

Inspect Settlement

One native NEAR core · deployed on testnet

Three responsibilities, one spending boundary.

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.

  1. 01Owner policy

    Direct owner controls: trusted services, blocks, purchase caps, daily caps, pause, and restricted sessions.

    Source moduleowner.rs
  2. 02Payment ledger

    Reserve before dispatch, bind the exact invoice, and finalize once from a private callback.

    Source modulepayments.rs
  3. 03Service registry

    Versioned supplier identity and issuer credentials scoped to one capability and conformance suite.

    Source moduleregistry.rs

One trust layer.Every agent payment.

/ Unparalleled performance

Supplier identity, owner limits, and capability evidence gate dispatch. Native receipts track settlement. The chart is decorative; no performance benchmark is claimed.

Native asset
NEAR
Core contract
1
Settlement model
Receipts
Build stage
Prototype

A bounded tool call.

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.

Choose a supplier.Keep control.

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.

/ One native coreOwner policy stays on the payment path.
/ Custom HTTP 402Custom adapter built; no standard-exact claim.
/ Controlled demonstrationTwo controlled providers, one invoice-audit capability.

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.

Payment Steps

An agent can choose the next useful service.Its owner decides the spending boundary.

AgentTrust connects the steps with reservations on NEAR.

Check beforedispatch.

Ask about AgentTrust

These links open an external AI with a project summary. Check current implementation status in the documentation.