How does Hilt use x402?

Hilt uses x402 as the HTTP 402 Payment Required protocol for protected resources. The response gives agents a machine-readable payment requirement; at launch, Hilt verifies the resulting Solana USDC settlement and turns it into receipt, entitlement, webhook, support, and audit state.

What does Hilt add to x402?

Hilt adds the operating layer around the payment: payment session, proof handling, Solana USDC settlement verification, receipt, entitlement, webhook, support context, analytics, and audit history.

Can x402 be used for AI agents and APIs?

Yes. The strongest Hilt Pay API use case is a protected API endpoint that returns HTTP 402 when unpaid, lets an agent pay, then checks Hilt entitlement before serving the resource.

x402 and Hilt Pay API

HTTP 402 payments that turn into real access.

x402 gives agents and APIs a standard way to say payment is required. Hilt Pay API turns that requirement into the full operating record: payment session, proof, Solana USDC settlement, receipt, entitlement, webhook, support context, and audit trail.

Open Hilt Pay API docs View API pricing

Protocol flow

x402 gives agents the payment requirement.

HTTP 402 response: machine-readable payment requirement

Launch settlement path: Solana USDC

Hilt: proof, receipt, entitlement, webhook, support, audit

Protected-resource loop

The API says payment required. Hilt makes the result operational.

Agent requests resource

An agent or backend calls a protected endpoint such as /ai/pro or /v1/private-data.

Server returns HTTP 402

If unpaid, the merchant backend returns a Hilt-created x402 requirement with the amount, product, and settlement details.

Buyer pays on-chain

At public launch, Hilt uses x402 payment requirements with Solana USDC settlement.

Hilt verifies and records

Hilt verifies settlement, issues receipt state, records proof, and activates the entitlement when the evidence binds correctly.

Product unlocks

The backend checks entitlement, serves the resource, and receives signed webhook and audit context for operations.

x402 is the payment-required protocol

It gives agents a machine-readable way to understand what must be paid before an API, dataset, bot, or private tool responds.

Settlement is still a rail decision

For Hilt Pay API public launch, the live settlement claim is Solana USDC. Base, selected EVM chains, and USDT remain production-gated until announced.

Hilt is the operating layer

The valuable part is not only the payment requirement. It is the receipt, entitlement, webhook, support trail, analytics, and audit record after payment.

Copyable shape

A clean 402 response for agents.

The response gives agents the exact payment requirement and the launch settlement details in one machine-readable shape.

HTTP/1.1 402 Payment Required

{
  "payment_protocol": "x402",
  "settlement_rail": "solana_usdc",
  "payment_session": "aps_...",
  "payment_requirement": {
    "amount": "9.00",
    "asset": "USDC",
    "network": "solana",
    "resource": "/ai/pro"
  }
}