Hilt Pay API

Turn a payment into permission.

Build paid APIs and agent services that challenge, settle, record, authorize, consume, and return the result in one replay-safe flow.

Paid requestSolana USDC
GET /research HTTP/1.1

HTTP/1.1 402 Payment Required

PAYMENT-REQUIRED: <x402 terms>

merchant server

POST /v1/access/x402/settle

POST /v1/access/entitlements/consume

HTTP/1.1 200 OK
{ "consumed": true, "units": 1 }

The complete loop

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

Check. Challenge. Pay. Settle. Consume. Serve.

1/6

Challenge

HTTP 402

2/6

Pay

Solana USDC

3/6

Settle

Verified proof

4/6

Record

Receipt

5/6

Consume

Atomic usage

6/6

Serve

Paid result

Live agent interfaces

Build with Hilt. Pay through Hilt. Call a paid Hilt API.

These are separate public contracts: Hilt Pay API runs paid access, PayMe MPP pays a verified recipient, and Transaction Evidence is a working paid resource operated by Hilt.

PayMe MPP

Pay a verified X handle from a wallet-capable agent.

The public action returns an MPP HTTP 402 charge for SOL or Solana USDC. The agent validates the exact terms, signs under its wallet policy, retries safely and receives the Hilt receipt.

POST https://api.hilt.so/v1/pay-me/payments

Read the PayMe agent guide

Hilt-operated paid resource

Fetch normalized finalized Solana transaction evidence.

Submit one transaction signature and receive structured chain evidence after a 0.05 USDC x402 V2 payment. No Hilt account or buyer API key is required.

POST https://www.hilt.so/v1/solana/transaction-evidence

What Hilt runs

Paid request runtime

Sell a configurable bundle of usage units in one payment, then atomically consume one unit per request and return HTTP 402 only when more usage is needed.

Receipts and entitlements

Keep settlement evidence separate from current authorization so software never has to infer access from a wallet transfer.

Signed events

Send payment, entitlement, and lifecycle events to the merchant backend with a verifiable support trail.

Agent-readable setup

Give agents structured discovery, OpenAPI, SDKs, examples, and sandbox flows while the owner retains live approval and credentials.

Developer resources

Everything technical lives here.

Start with the guide. Drop into schemas, packages, MCP, and discovery files only when your integration needs them.

Hosted Hilt Pay API sessions can settle in native SOL or Solana USDC using separate products for each asset. x402 V2 remains a Solana USDC protected-resource flow. Buyers sign with their own wallets and merchants settle directly to their configured payout wallets.

Zero custody
Already have a Hilt Pay API account?Sign in to manage apps and credentials

Build the paid request

Prove it in sandbox. Move live when the owner is ready.

Compare API plans