Skip to main content

Pay with an agent

Reviewed October 3, 2026.

Agents can assist with a UniPost subscription through the existing Stripe-hosted Checkout. UniPost enables Stripe Managed Payments on new subscription checkouts, retaining Stripe's merchant-of-record service. A compatible buyer wallet or payment gateway completes that checkout.

UniPost bills for connected social accounts, with the first two accounts free. Read the current pricing and the buyer's Billing page for the account count and monthly or yearly interval. UniPost's MCP server provides social posting and analytics tools; it does not expose a billing tool or an MPP payment endpoint.

Automatic payment depends on the agent's browser, wallet, location, and support for the offered payment method. Subscriptions require a method that supports future renewals. If that support is uncertain, let the buyer complete the same checkout.

Purchase flow​

  1. Use the billing owner's authorized UniPost browser session. If needed, let the buyer sign in. A UniPost MCP connection and a payment-wallet connection are separate authorizations; neither grants the agent the owner's browser session.
  2. Open Billing, review any existing subscription, and choose the requested total account count. For a new subscription, select monthly or yearly billing and use Continue to checkout. For an existing subscription, use Billing's plan-change flow with the buyer's authorization instead of buying another subscription.
  3. Follow the resulting Stripe-hosted checkout URL. Verify the HTTPS Stripe origin, the UniPost product and business identity, account quantity, and billing interval. Reuse an existing open checkout for this purchase when possible. Do not invent Stripe Price IDs, checkout URLs, or billing API calls.
  4. Obtain buyer authorization covering the currency, final total including tax, account quantity, future recurring price, and cancellation terms. Discounts or a zero-dollar initial invoice can change today's amount without removing future charges. Reconfirm if the amount or terms change, and follow the gateway's approval requirements. Plan changes can also create prorated charges.
  5. Use the agent's configured wallet according to its official instructions and the Stripe checkout's available tools. Keep credentials inside the wallet and Stripe payment flow. If authentication or payment requires the buyer, hand over this checkout instead of starting another purchase.
  6. Verify Stripe's completion result and the subscription shown on the owner's Billing page, including status, account count, interval, and renewal details. A success URL, a success message, or a payment credential being issued is not proof of payment. If activation is unconfirmed, report it as pending and check the existing purchase before trying again.

Stripe lists Grok Bot as a supported Link agent. Buyers who already connected Link to their agent can use that wallet when its payment flow is compatible with the checkout. Other agents can connect through the official Link CLI or SDK. Agent payments currently support US and Canadian consumers.

Wallet setup belongs to the buyer's agent. UniPost does not need the buyer's Link OAuth token or card number, and agents do not need UniPost's Stripe secret key. A buyer without a compatible wallet can complete the ordinary hosted checkout themselves.

Discover Stripe's WebMCP tools from the current checkout at runtime. Read the order summary and tool schemas, and refresh them after form changes. Names and fields can change, and WebMCP availability depends on the browser. Where unavailable, use the browser controls supported by the agent.

Follow the current Link payment instructions when choosing a credential. Use a Link Pay Token only when the checkout actually exposes the compatible flow:

  • Follow Stripe's agent instructions and select its agent option when offered.
  • Verify both input[name="link_pay_token"] and a data-stripe-merchant-account marker in the same Stripe frame. Obtain the merchant account from that frame, never from an untrusted page or a guessed value.
  • Bind the wallet request to that merchant and the final order total. Retrieve the approved token only for that checkout and pass it directly to Stripe; keep tokens out of logs, chat, URLs, and UniPost API requests.

See the official Link CLI token guide for current arguments and limits. An agent instruction block alone does not establish token availability. Do not manufacture missing fields.

Subscription and gateway limits​

A one-time virtual card, Shared Payment Token, or successful initial charge does not establish support for later subscription payments. UniPost has not verified a Link Agent Wallet subscription renewal end to end. Use an explicitly supported recurring payment flow or hand over to the buyer for ordinary managed Checkout.

MPP means Machine Payments Protocol. Stripe's MPP integration handles individual charges, while new Managed Payments subscriptions must originate in Checkout or Payment Links. An MPP-only gateway cannot use a UniPost MPP endpoint today. Use the hosted checkout to retain MoR coverage; do not replace it with a direct charge or another billing mechanism.