​
Connect Hilt PayMe to a compatible AI client

The Hilt PayMe remote MCP server lets a compatible AI client understand ordinary payment instructions, resolve verified PayMe recipients, prepare exact payment terms, and read payment activity. The AI does not hold payment authority. It returns a Hilt approval page, and the payer reviews and signs with Phantom, Solflare, Backpack, Trust Wallet, or SafePal on mobile, or a supported browser wallet such as Jupiter on desktop. The payer does not need a PayMe account.
Client support and connector menu names vary. Hilt provides a standard remote MCP endpoint and OAuth authorization flow; each AI client controls how custom MCP servers are installed and displayed.

​
Add the connector

  1. Open the connector, integration, or tools settings in a compatible AI client.
  2. Add a custom remote MCP server.
  3. Enter this URL:
  1. Continue to Hilt when the client opens the OAuth flow.
  2. Sign in with X and approve the requested PayMe scopes.
  3. Return to the AI client and keep the Hilt PayMe connector enabled.
  4. Optionally create a receiving profile if you want people to pay your X handle or want the connector to create payment links for you.
No payment is made during connector setup. X OAuth identifies the connected user and their connector activity. A receiving-wallet signature is required only when adding a wallet where payments to that user’s own handle should arrive.

​
Confirm the connection

Ask:
The client calls hilt_pay_me_account and returns the connected X identity plus any optional receiving profile. This checks the connector without preparing a payment. There is no special slash command. Use ordinary language:

​
What the connector can do

  • read the connected X identity and optional receiving profile
  • resolve an active Hilt PayMe profile by X handle
  • start a trackable SOL or Solana USDC payment to a verified PayMe handle
  • read sent and received payment activity
  • create an amount-specific payment link for the user to share
  • cancel an unapproved payment or unused payment link

​
What the connector cannot do

  • access a seed phrase or private key
  • sign or submit a wallet transaction
  • move funds without wallet approval
  • pay an X handle with no active Hilt PayMe profile
  • post or send a direct message on X
  • contact a named payer automatically
  • treat a typed X handle alone as a payout destination

​
Sending and receiving are separate

A user can authorize the connector with X and send without creating a PayMe receiving profile. The outgoing payer approves with Phantom, Solflare, Backpack, Trust Wallet, or SafePal on mobile, or a supported browser wallet such as Jupiter on desktop, and does not need a PayMe account. A receiving profile is needed only when the connected user wants payments sent to their own X handle or wants the connector to create PayMe links for them. The receiving wallet signs its own identity binding so an X account cannot assign a wallet it does not control.

​
Send a payment

Example:
The client calls hilt_pay_me_send_payment. Hilt returns:
  • a trackable payment ID
  • the recipient’s verified PayMe handle and receiving wallet
  • the exact asset, recipient amount, and 2% fee preview
  • a 30-minute wallet-approval expiry
  • a pay.hilt.so approval URL
The initial state is awaiting_wallet. It is not a receipt and does not mean funds have moved. The payer opens the URL, reviews the full terms, and approves with Phantom, Solflare, Backpack, Trust Wallet, or SafePal on mobile, or a supported browser wallet such as Jupiter on desktop. Hilt then exposes authorization or confirmation state and the Solana transaction signature when available.

​
Check payment activity

Examples:
hilt_pay_me_get_payment reads one outgoing payment. hilt_pay_me_list_activity returns recent sent and received activity. Hilt distinguishes awaiting wallet approval, wallet-authorized checkout, confirmed settlement, expiry, cancellation, and a known failed checkout. Example:
hilt_pay_me_create_payment_link returns a link for the connected user to share. Hilt does not message, mention, post to, or otherwise contact another X account. Payment links expire after 72 hours by default. The connector may set an expiry from 1 to 168 hours. An unused link can be checked or cancelled before a payer authorizes the checkout.

​
Connector tools

​
OAuth permissions

Connector access tokens are accepted only by the PayMe MCP resource. They are not dashboard sessions, Hilt Pay API keys, or wallet credentials.

​
Current asset scope

The exact send-payment and payment-link tools support:
  • native SOL
  • Solana USDC
The wider PayMe checkout may display supported tokens held by the payer’s wallet. The connector does not advertise a custom token for an exact send command unless Hilt can bind and validate its mint terms. This connector is separate from Hilt Pay API /v1/access. It does not create API entitlements or x402 metered access.

​
Discovery endpoints

  • MCP resource: https://api.hilt.so/mcp/pay-me
  • OAuth protected-resource metadata: https://api.hilt.so/.well-known/oauth-protected-resource/mcp/pay-me
  • OAuth authorization-server metadata: https://api.hilt.so/.well-known/oauth-authorization-server
  • PayMe builder: https://pay.hilt.so/me
  • PayMe agent pack: https://pay.hilt.so/agent-pack.json