NewMetered agent payments are liveRead the technical release

Hilt Pay API · HTTP 402 paid access

Payment-to-access infrastructure for agents, APIs and stablecoin commerce

Hilt turns HTTP 402 into a complete paid request: the buyer agent pays, Solana USDC settles, Hilt records the receipt, grants entitlement, atomically consumes one usage unit, and the API returns the result.

The payment is the middle of the request, not the end.

Build a metered endpointSee the paid-request loop
Zero-custody settlementApproved for the Alchemy Solana Fund

Paid-request runtime

x402 V2 · Solana USDC · zero custody

  1. 01

    Request

    GET /research

    usage units: 0

  2. 02

    Challenge

    402 PAYMENT-REQUIRED

    Solana USDC terms

  3. 03

    Pay

    PAYMENT-SIGNATURE

    buyer wallet signs

  4. 04

    Settle

    payment verified

    receipt + entitlement

  5. 05

    Consume

    units: 1

    atomic usage event

  6. 06

    Serve

    200 OK

    paid result returned

The merchant's scoped Hilt key stays server-side. The buyer agent validates the advertised terms and signs from its own wallet.

Request. Challenge. Pay. Settle. Consume. Serve.

Challenge

GET /research
HTTP/1.1 402 Payment Required
PAYMENT-REQUIRED: <Hilt x402 V2 terms>

Successful retry

GET /research HTTP/1.1
PAYMENT-SIGNATURE: <buyer-signed transaction>

merchant server:
POST /v1/access/x402/settle
POST /v1/access/entitlements/consume
{ "consumed": true, "units": 1 }

protected resource:
HTTP/1.1 200 OK

Reference implementation

Run the public buyer-agent and protected-resource example against local, sandbox, or live mode.

Run the reference implementation

Beyond the transaction

Hilt completes the paid-request loop for metered agent services on Solana.

x402 defines the HTTP payment requirement. Solana USDC provides Hilt's current live settlement path. Hilt connects that settlement to the receipt, entitlement, and atomic usage state that determine whether a protected service can return billable work.

Atomic usage authority

Each billable request is served only after Hilt atomically consumes the required entitlement unit.

Retry-safe settlement

Idempotent settlement can reconcile a finalized transaction without asking the buyer agent to pay again.

Complete operating record

Payment, receipt, entitlement, usage, webhook, support context, analytics, and audit state stay connected.

Zero custody

The buyer pays from its own wallet and merchant proceeds settle directly to the configured payout wallet.

Hilt Pay API

The code-first surface for agents, APIs, tools and data.

Build payment sessions, HTTP 402 requirements, settlement, receipts, entitlements, atomic usage, webhooks, support context, and audit history under the public `/v1/access` namespace.

Explore Hilt Pay APIAPI pricing

Hilt Pay Workspace

The dashboard-led surface for merchants.

Run hosted checkout, memberships, native subscriptions, downloads, WooCommerce, receipts, analytics, support, and webhooks from one operating view.

Open Hilt Pay Workspace

Paid-request implementation

One paid request. Three fail-closed gates.

Payment proof alone is not permission to serve. Settlement and atomic usage consumption must both succeed before the protected result leaves the merchant's server.

01

Request and meter

The protected server attempts to consume one entitlement unit before running billable work.

02

Challenge and settle

When usage is missing, return HTTP 402. The buyer signs the advertised Solana USDC terms and the server settles through Hilt.

03

Consume and serve

Hilt verifies settlement, records the receipt, grants entitlement, and atomically consumes one unit before the API returns the result.

Integrations

Start with production-ready paths today, with more automation on the way.

Developer tools

WooCommerce

Available now

Connect WordPress digital products, memberships, and access offers to Hilt checkout with the free WooCommerce plugin.

WooCommerce plugin

Webhooks and SDKs

Available now

Use signed webhooks plus the JavaScript, TypeScript, and Python SDKs to connect Hilt payment and entitlement state to your product.

Developer tools

Zapier

Coming soon

Send Hilt events into the automations a merchant already uses for CRM, email, fulfilment, reporting, and support.

Zapier updates

Where Hilt fits

Sell a machine request or run human checkout from the same core.

AI agents and tools

Sell a defined unit of research, inference, generation, automation, or another agent-delivered result without a human checkout loop.

See the paid-request loop

APIs, data and MCP tools

Protect API calls, datasets, private endpoints, MCP tools, and usage bundles with payment requirements software can understand.

Build with Hilt Pay API

Human-operated commerce

Use Hilt Pay Workspace for hosted checkout, memberships, downloads, WooCommerce, native subscriptions, receipts, analytics, and support.

Explore Hilt Pay Workspace

Merchant workspace

The human operating view for stablecoin commerce.

Hilt Pay Workspace gives operators the dashboard around the infrastructure: products, checkout, members, receipts, analytics, support context, subscription state, webhooks, and billing signals in one operating view.

Open the appCompare plans

Merchant cockpit

See what sold and what needs attention.

The workspace brings live templates, receipts, member records, subscription state, and support context into one operating view.

Analytics

Read the funnel without exporting a spreadsheet first.

Revenue, checkout opens, confirmed payments, sources, subscription state, and product-level pressure points stay visible.

Product pressure

Find the product that needs attention.

Revenue, funnel, subscription, delivery, and support signals sit together so merchants can decide what to tune next.

Hilt Pay API pricing

Start in sandbox. Add live settlement when the paid loop is ready.

Prove the HTTP 402, settlement, receipt, entitlement, and usage flow without moving live funds. The paid API plans add live Solana USDC settlement, lower fees, deeper operating history, and more support.

Full API pricingWorkspace pricing
PlanBest forMonthlySolana USDC fee

Sandbox

Building and testing

Free

No live money

Starter

First production endpoint

$79/mo

1% Solana USDC fee

Growth

Growing paid services

$349/mo

0.7% Solana USDC fee

Scale

High-volume infrastructure

$1,250/mo

0.45% Solana USDC fee

Common questions

Direct answers before an owner or agent goes live.

Keep ownership, credential, settlement, and access boundaries explicit before autonomous requests begin.

Read full FAQ

How does Hilt handle a metered agent request?

The protected server tries to consume one usage unit, returns HTTP 402 when usage is missing, settles the buyer's PAYMENT-SIGNATURE through Hilt, then consumes one unit and serves only after settlement and consumption succeed.

Does the buyer agent receive the merchant's Hilt API key?

No. The merchant keeps its scoped Hilt credential inside the protected server or controlled server-side agent. The buyer agent reads the payment requirement and signs from its own wallet.

Does Hilt hold the buyer's USDC?

No. The buyer signs from its own wallet. Merchant proceeds settle directly to the configured payout wallet while Hilt verifies payment and records the operating state around it.

Is x402 the settlement rail?

No. x402 is the HTTP 402 protected-resource protocol shape. Solana USDC is Hilt Pay API's current public live settlement path.

Turn one protected endpoint into a complete paid request.

Start free in sandboxOpen developer guide