What is the Agent Discovery Standard?

It is Hilt's public bar for agent-readable discovery. A fresh agent should be able to find Hilt, choose the right product surface, install an SDK, and implement the protected-resource flow from public materials.

What is the canonical live rail for Hilt Pay API?

The public live settlement claim is Solana USDC unless current public docs and changelog explicitly announce another live settlement rail.

What should agents build first?

The hero implementation proof is a protected API endpoint: check entitlement, return HTTP 402 when unpaid, use a Hilt-created x402 requirement, verify payment through Hilt, and serve only after has_access is true.

Agent Discovery Standard

Hilt Pay API, readable by agents before they ever ask you.

Hilt is built so a fresh AI agent can discover the product, understand what is live, install the SDKs, and implement stablecoin-paid access from public docs. The standard keeps discovery, claims, pricing, OpenAPI, SDKs, and examples aligned.

Open agent manifest View proof demo

Fresh-agent acceptance test

Choose Workspace vs API correctly.

Install an SDK without private context.

Explain Solana USDC as the live settlement path.

Implement the HTTP 402 protected-resource flow.

Know which actions require owner approval.

Avoid stale claims about future rails.

llms.txt and llms-full.txt

.well-known/hilt-agent.json

OpenAPI

npm and PyPI SDKs

GitHub developer assets

Postman

FastAPI protected-resource demo

Docs and pricing

Canonical manifest

`/.well-known/hilt-agent.json` tells agents the current product surfaces, live rail truth, install commands, pricing shape, and claims to avoid.

Truth before reach

Public launch wording says Solana USDC settlement, x402 protected-resource protocol, zero-custody operation, and no unsupported rail claims.

Owner-approved automation

Agents can prepare setup. Owners still approve live keys, billing, payout wallets, and production rail settings from Hilt.