Back to blog

AGENTTRUST

An agent can choose a supplier. Its owner sets the boundary.

An agent needs an invoice CSV audited. It can compare services and request a quote. That choice should not give it authority to pay any account, use a different asset, or spend beyond the owner's allowance.

AgentTrust on NEAR puts that boundary in a native contract. The owner configures trusted suppliers and blocks, purchase and daily limits, and the capability evidence required by a session. A restricted function-call key can call only the core's payment method with zero attached deposit. Owner management stays separate.

A supplier is an exact identity

A service record binds an account and version to a signing key, payout account, and endpoint commitment. The signed invoice also binds the buyer, session, profile, policy revision, exact request hash, native amount, and stable payment ID.

Registration does not grant trust. The owner must permit the exact supplier identity. A profile may also require a current credential from an accepted issuer for the named capability and conformance suite. These are explicit permissions and evidence checks, not a reputation score.

One bounded demonstration

The controlled testnet demonstration uses two providers of invoice.audit.v1. The audit engine parses CSV, reports duplicate invoice groups and rejected rows, and computes exact per-currency totals. Totals include valid duplicates and are explicitly not payable amounts.

The project-operated validator tests named public fixtures and checks a supplier-signed identity challenge. Passing the suite says only that those fixtures passed at that time. It does not attest to arbitrary future provider behavior.

What is verified today

The r2 testnet capture records a deployed core, two settled native payments, contract refusals, an exact retry without a second payout and a checked report. Its MCP buyer was scripted. Two fresh r3 and r4 operator rehearsals each record a local-model request for host-allowed B after A's read-only missing-credential preview, a separate settled 0.002 NEAR purchase, direct contract refusals and a native retry. The host supplied the original payment ID and CSV. Separate native runtime captures support 20 of 21 case groups; the refund-gap remains open. The public website feed shows dated on-chain decisions, and paid providers/MCP/model buyer remain local. Browser visual QA remains open.

The visual website and docs shell are reused from the upstream AgentTrust project. The NEAR integration is new work, recorded separately in the repository's build ledger and baseline tags.