Reputation

Trust signals derived from the merchant’s audit log

The reputation endpoint exposes trust signals for buyer agents to evaluate a merchant before transacting.

Endpoint

GET /reputation

Authentication: None — this endpoint is publicly accessible.

Response

{
  "agent_name": "data",
  "success_rate": 0.97,
  "total_transactions": 142,
  "successful_transactions": 138,
  "failed_transactions": 4,
  "uptime_hours": 720,
  "last_transaction": "2026-03-30T18:45:00Z",
  "average_response_time_ms": 250
}

Response Fields

agent_name · string

The merchant’s agent name.

success_rate · number

Percentage of successful x402 transactions (0.0 to 1.0).

total_transactions · number

Total number of x402 payment requests processed.

successful_transactions · number

Number of transactions that completed successfully.

failed_transactions · number

Number of transactions that failed (payment verification failures, timeouts, etc.).

uptime_hours · number

Total hours the server has been running.

last_transaction · string

ISO timestamp of the most recent transaction.

How Buyer Agents Use This

The check_reputation MCP tool fetches this endpoint and returns the data to the agent. A buyer typically:

1. Checks success_rate — is the merchant reliable?
2. Checks total_transactions — is the merchant established or brand new?
3. Checks last_transaction — is the merchant actively serving traffic?

A high success rate with meaningful transaction volume is a strong trust signal.