TrustGate
Trust-aware x402 payments for autonomous AI agents on Hedera.
Demo
About
TrustGate is a reputation-aware payment layer for autonomous AI agents built on Hedera. It extends x402 pay-per-request payments with a verifiable trust mechanism that evaluates an agent's transaction history before deciding how its payment should be handled. When an agent discovers and requests a paid service, TrustGate checks its on-chain reputation. New or low-reputation agents are routed through a protected payment flow using Hedera Scheduled Transactions, allowing the payment to be held while the service is delivered and resolved according to the escrow policy. Agents with an established history of successful interactions can use the standard x402 settlement path with significantly lower friction and latency. Each payment, delivery outcome, and trust decision is recorded through Hedera Consensus Service (HCS), creating a publicly verifiable audit trail. This gives autonomous agents a way to progressively establish trust through successful transactions rather than relying solely on static identities or centralized reputation systems. The MVP demonstrates an end-to-end agentic commerce flow: service discovery, x402 payment, reputation evaluation, adaptive settlement, service delivery, and on-chain reputation updates. TrustGate's core idea is simple: **the more an agent proves it can transact successfully, the less friction it faces when paying for services.**
How it's made
TrustGate is a TypeScript/Node.js payment router for autonomous agents, built around Hedera Testnet and x402. We use @x402/core + @x402/hedera to generate and sign x402 v2 HBAR payments, and Blocky402 as the Hedera facilitator for verification/settlement. Hedera Scheduled Transactions provide the protected payment path, while an in-memory reputation engine records successful payments and routes agents from PROTECTED to STANDARD once they reach a trust threshold. A particularly hacky part was adapting the x402 v2 payment envelope to Blocky402’s Hedera-specific verification requirements and dynamically incorporating its fee-payer configuration.