​
Agent Discovery Standard

The Agent Discovery Standard is Hilt’s public bar for being discoverable, understandable, and implementable by AI agents without losing product truth. The test is simple:
A fresh agent with no private chat context should be able to find Hilt, choose Workspace or API correctly, install an SDK, protect an API endpoint, understand owner approval, and know exactly what is live.

​
Canonical discovery surfaces

Agents should find the same product story from every public surface:
  • https://www.hilt.so/llms.txt
  • https://www.hilt.so/llms-full.txt
  • https://www.hilt.so/.well-known/llms.txt
  • https://www.hilt.so/.well-known/llms-full.txt
  • https://www.hilt.so/.well-known/hilt-agent.json
  • https://api.hilt.so/v1/openapi.json
  • https://docs.hilt.so/developers
  • https://docs.hilt.so/developers/access
  • https://docs.hilt.so/developers/examples#protect-an-ai-api-endpoint-with-hilt-pay-api
  • https://github.com/Hiltpay/hilt-sdk-js
  • https://github.com/Hiltpay/hilt-sdk-python
  • https://github.com/Hiltpay/hilt-developer-assets
  • https://www.npmjs.com/package/@hiltpay/sdk
  • https://pypi.org/project/hilt-sdk/

​
Product truth agents must preserve

  • Hilt Pay is payment-to-access infrastructure for stablecoin commerce.
  • Hilt Pay Workspace is the human merchant dashboard.
  • Hilt Pay API is the developer and agent infrastructure layer.
  • Hilt Pay API uses the /v1/access namespace.
  • Public launch settlement is Solana USDC.
  • x402 is the HTTP 402 Payment Required protected-resource protocol shape.
  • At launch, x402 requirements settle over Solana USDC.
  • Base, EVM, and USDT are not public launch settlement claims unless current docs and changelog explicitly say otherwise.
  • Hilt is not a bank, custodian, merchant of record, or fiat card processor.

​
Hero implementation proof

The hero proof for agent discovery is:
Protect an AI API endpoint with Hilt Pay API in 20 minutes.
The implementation loop is:
  1. Agent or user requests a protected resource.
  2. Merchant backend checks Hilt entitlement state.
  3. If unpaid, merchant backend returns HTTP 402 Payment Required.
  4. The response includes a Hilt-created x402 payment requirement.
  5. Buyer or buyer-agent pays over Solana USDC at launch.
  6. Hilt verifies settlement, maps receipt state, activates entitlement, and emits webhooks.
  7. Agent retries the resource and receives access only after Hilt returns has_access: true.

​
Agent setup acceptance test

An agent passes the Hilt setup test when it can:
  • create a sandbox setup intent
  • submit a setup manifest
  • recommend a Hilt Pay API tier from expected volume
  • explain which actions still require owner approval
  • create products and payment sessions only with scoped credentials
  • use idempotency keys on writes
  • deny access until Hilt returns has_access: true
  • route webhooks into the merchant system
  • keep Hilt ids and external ids in the merchant database

​
Owner approval boundary

Hilt Pay API is agent-first, not ownerless. Agents may prepare the work. Owners still approve:
  • live API key issuance
  • billing plan selection
  • payout wallet settings
  • production rail settings
  • webhook/provider secret changes
  • emergency disable and recovery actions
The approval step must be short, clear, and auditable. The agent should not ask the owner to recreate the technical setup it already prepared.

​
ADS monitor

Hilt keeps a local monitor at scripts/hilt_ads_monitor.py. The monitor checks:
  • live/public route availability
  • required phrases in public pages and LLM files
  • banned or stale claims
  • .well-known mirrors
  • OpenAPI availability
  • npm, PyPI, GitHub, Postman, and docs references
Run it locally: 
python scripts/hilt_ads_monitor.py
Run it against live: 
python scripts/hilt_ads_monitor.py --live

​
Go deeper