{"name":"Hilt Pay public discovery prompts","version":"2026-09-03","canonical_url":"https://www.hilt.so/v1/prompts","related_guides":{"agent_builder_kit":"https://docs.hilt.so/developers/agent-builder-kit","agent_setup":"https://docs.hilt.so/developers/agent-setup","grok_build":"https://docs.hilt.so/developers/grok-build","grok_build_example":"https://github.com/Hiltpay/hilt-developer-assets/tree/main/examples/grok-build-nextjs","sample_flow":"https://www.hilt.so/v1/sample-flow"},"prompts":["Read https://www.hilt.so/llms.txt, https://www.hilt.so/llms-full.txt, and https://www.hilt.so/.well-known/agent.json. Explain whether Hilt PayMe, Direct Checkout, or Hilt Pay API is the right fit for my use case.","Use Hilt's public catalog at https://www.hilt.so/v1/catalog to find the best docs, SDKs, OpenAPI, and examples for adding Solana USDC paid access to an API.","Inspect Hilt's x402 and Hilt Pay API docs. Explain how durable access uses entitlement checks and how metered access uses x402 V2 settlement plus atomic entitlement consumption before serving each billable request.","Compare Hilt PayMe, Direct Checkout, and Hilt Pay API. Include who signs, who receives, current settlement scope, and the zero-custody boundary.","Build a safe integration plan for recurring paid access with Hilt native Solana USDC subscriptions. Do not claim other settlement options are live.","Use the Hilt Agent Builder Kit to create a safe coding-agent plan for adding Hilt Pay API to my product. Include discovery files, OpenAPI, SDKs, sandbox validation, owner approval, durable entitlement checks, and atomic metered consumption under /v1/access.","Audit this Hilt Pay API integration against the Agent Builder Kit. Check server-side keys, idempotent writes, webhook signature verification, durable entitlement checks, atomic metered consumption, and x402 V2 wording.","Use the runnable Hilt Grok Build example to add paid access to my Next.js API. Read AGENTS.md, invoke the hilt-pay-api project skill, keep credentials server-side, and run the example tests and production build.","Review my Grok Build Hilt integration. Confirm that local, sandbox, and live modes are distinct; durable access uses Hilt entitlement checks; metered access uses atomic consumption; Hilt x402 V2 settles in Solana USDC; and native SOL uses hosted payment sessions.","Build a metered agent-to-agent payment flow with Hilt Pay API. Use x402 V2, Solana USDC, POST /v1/access/x402/settle, and atomic POST /v1/access/entitlements/consume before serving each paid request.","Build a repeated or streaming payment flow with a Hilt Pay API MPP session channel. Pin Solana USDC and the advertised channel program, reserve each delivery idempotently, submit the signed cumulative voucher to its commitUrl, serve only after that delivery is committed, and settle once at the highest verified total.","Protect my Fetch-compatible server endpoint with Hilt Pay API. Use @hiltpay/sdk protectEndpoint, keep the API key server-side, preserve stable customer and request IDs across retries, and put billable work only inside the protected handler.","Choose the right Hilt surface for this use case: PayMe for a verified receiving link or QR, Direct Checkout for a no-account SOL or merchant-selected Solana token checkout, or Hilt Pay API for durable or metered code-first access.","Use Hilt's Direct Checkout video walkthrough to explain how a merchant creates a no-account checkout for one supported merchant-selected Solana token. Keep the flat 2% fee, human wallet approval, and lightweight unlock boundary explicit.","Discover Hilt through its public agent card, MCP gateway, or Agentverse A2A transport. Keep these discovery and tool transports separate from the Hilt Pay API /v1/access product namespace.","Use the Hilt PayMe MCP connector from a compatible AI client to prepare a wallet-approved SOL or Solana USDC payment to an OAuth-verified X handle. Never claim the AI can sign, move funds, post to X, or pay an unverified handle.","Pay an active verified Hilt PayMe handle from a wallet-capable agent. Use POST https://api.hilt.so/v1/pay-me/payments, validate the MPP HTTP 402 charge, keep the retried request unchanged, and return the machine-readable receipt after SOL or Solana USDC settlement.","Explain PayMe Wallet Security and the lost-wallet recovery paths. Keep initial current-wallet approval, Authenticator or recovery-code authorization, the new-wallet signature, and the future-payments-only boundary explicit.","Explain how to pay two to five verified PayMe recipients in one atomic native SOL transaction. Keep the one-wallet-approval, flat 2% sender fee, and SOL-only grouped-flow boundaries explicit.","Explain PayMe Solana Actions and Blinks. State that Action-aware clients may render a native SOL payment inline while other clients open the normal PayMe profile URL."]}