​
Solana transaction evidence

Hilt operates a public paid endpoint that turns one finalized Solana transaction into a compact, machine-readable evidence record. Use it when an agent or backend needs consistent public-chain facts without maintaining its own transaction parser:
  • finality outcome, slot, timestamp, and network fee
  • transaction signers and invoked program IDs
  • exact native SOL balance changes
  • exact token balance changes with mint and decimal precision
  • parsed top-level and inner transfer instructions when Solana RPC provides them
  • warnings when evidence is missing, ambiguous, or belongs to a failed transaction
The endpoint costs 0.05 USDC per request and uses standard x402 V2 exact settlement on Solana mainnet. It requires no Hilt account or API key from the buyer.

​
Endpoint

Create a fresh request_id for each new paid lookup. Reuse the same value only when retrying that exact lookup after 402 Payment Required or a transport failure. This keeps payment settlement and usage consumption retry-safe. The first valid request returns HTTP 402 with a base64-encoded PAYMENT-REQUIRED header. A compatible x402 client validates the Solana USDC terms, obtains wallet approval, and retries the same request with PAYMENT-SIGNATURE. Hilt verifies settlement, records the receipt and entitlement, atomically consumes the lookup unit, and only then returns the evidence response.

​
Pay CLI example

The Pay CLI can handle the challenge and wallet-approved retry:
Confirm the displayed recipient, Solana network, USDC mint, and 0.05 USDC amount before approving.

​
Response boundary

The endpoint reports evidence present in a finalized public Solana RPC response. It does not label a wallet, token, transaction, counterparty, or payment as universally safe, legitimate, or legally compliant. A successful transaction can still represent an unwanted or misunderstood action. A failed transaction can still charge a network fee. Applications should apply their own expected-recipient, expected-asset, expected-amount, business-context, and risk policies to the returned evidence.

​
Machine-readable contract

For developers building their own paid endpoint, see Protect an endpoint and Agent-to-agent micropayments.