Paid request runtime
Return an HTTP 402 payment requirement, settle the buyer-signed transaction, consume one usage unit, then serve the result.
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 }
{ "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
What Hilt runs
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.
Start here
Hilt Pay API guide
Copy a working flow
Metered agent request guide
Inspect the contract
OpenAPI schema
Install TypeScript
@hiltpay/sdk
Install Python
hilt-sdk
Connect an agent
Hilt MCP gateway
Read discovery
Agent manifest
Test without money
Sandbox quickstart
Live settlement is Solana USDC. x402 describes the HTTP 402 protected-resource exchange. 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