Connect Hilt Pay Me to Grok

Hilt Pay Me lets a Grok user create payment requests and prepare payments using OAuth-verified X handles. Hilt resolves the recipient, prepares the exact terms, and sends the payer to a Hilt approval page. The payer reviews and signs in their own wallet.
Hilt and Grok are separate products. This guide documents compatibility with Grok custom MCP connectors. It does not describe an xAI partnership.

What the connector does

The connector can:
  • read your OAuth-verified Hilt Pay Me identity and signature-verified receiving wallet
  • resolve an active Hilt Pay Me profile by X handle
  • create an amount-specific SOL or Solana USDC payment request for your profile
  • prepare a SOL or Solana USDC payment to another verified Pay Me handle
  • return share-ready X copy without posting it automatically
  • read open, expired, and paid request state
The connector cannot:
  • access a seed phrase or private key
  • sign or submit a wallet transaction
  • move funds without wallet approval
  • pay an X handle that has no active Hilt Pay Me profile
  • post or send a direct message on X
  • treat an X handle alone as a payout destination

Add the connector in Grok

  1. Open https://grok.com/connectors.
  2. Select New Connector, then Custom.
  3. Enter this MCP server URL:
  1. Continue to Hilt when Grok opens the authorization flow.
  2. Sign in with X. Hilt uses the stable OAuth account identity behind the handle.
  3. If you already have a Pay Me profile, Hilt loads it. If not, connect the wallet where payments should arrive and sign the wallet-verification message.
  4. Review the connector permissions and approve the connection.
No payment is made during connector setup. The receiving-wallet signature proves control of the payout address; it does not send a transaction.

Confirm the connection

After approving Hilt, return to Grok and ask:
Grok calls hilt_pay_me_account and returns the connected X identity and receiving-wallet status. This is the quickest check that the connector is ready; it does not create a request or prepare a payment. You can then use natural-language instructions such as:
There is no special slash command. Keep the Hilt Pay Me connector enabled for the conversation and tell Grok what you want it to prepare.

Automatic onboarding boundary

Hilt can automatically create or recover the Hilt account associated with the X OAuth identity. It can also recognize an existing Pay Me profile. A new user still performs one wallet action: connect the receiving wallet and sign its identity binding. That signature keeps an X account from assigning a wallet it does not control. After setup, Grok can prepare requests and payments without asking the user to re-enter their X handle or receiving wallet. Every outgoing payment still requires the payer to open Hilt, review the full terms, and approve in the payer’s wallet.

Ask Grok for a payment request

Example:
Grok calls hilt_pay_me_create_request. Hilt returns:
  • a request ID
  • the OAuth-verified recipient profile
  • the requested asset and amount
  • an expiry
  • a pay.hilt.so approval URL
  • share-ready text mentioning the intended X handle
The request link fixes the recipient, asset, amount, and note. Hilt Pay Me’s flat 2% fee and the final wallet total remain visible before approval. Payment requests expire after 72 hours by default. The connector may set an expiry from 1 to 168 hours.

Ask Grok to prepare a payment

Example:
Grok calls hilt_pay_me_prepare_payment. Hilt resolves @designer to an active OAuth-verified Pay Me profile and returns a prefilled approval URL. The response status is wallet_approval_required. It is not a payment receipt. The payment becomes complete only after the payer signs, Hilt confirms the finalized Solana transaction, and Hilt returns paid state or a receipt.

Connector tools

OAuth permissions

The connector requests three narrow scopes: Connector access tokens are accepted only by the Pay Me MCP resource. They are not dashboard sessions, Hilt Pay API keys, or wallet credentials.

Zero-custody payment sequence

Grok handles intent and preparation. The wallet retains payment authority.

Current asset scope

The Grok connector’s amount-specific request and preparation tools support:
  • native SOL
  • Solana USDC
The wider Hilt Pay Me checkout page can show supported tokens held by the payer’s wallet. The connector does not advertise a custom token as an exact prepared request unless Hilt can bind and validate its mint terms. This connector is separate from Hilt Pay API /v1/access. It does not turn Pay Me payments into API entitlements or x402 metered access.

Discovery endpoints

  • Pay Me 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
  • Pay Me builder: https://pay.hilt.so/me
  • Pay Me agent pack: https://pay.hilt.so/agent-pack.json