# Envoy in Grok

Follow the [complete installation guide](https://agent.envoy.money/host-installation.md#grok) for all hosts.

Skill and plugin release **0.4.15**, for the current Envoy tool contract (support revision `envoy@2026-10`). Last updated **3 November 2026**.

`pay-with-envoy` handles commerce; `check-envoy-account` handles explicit account questions. Each skill carries its own instructions and follows the `next` step in every Envoy tool reply; there is no separate guidance tool to load. Installing package files alone does not connect an account, select a default or authorize spending. This guide adds no payment, onboarding or recovery instructions.

Connecting lets this assistant read your Envoy account and ask to buy. It does not approve a purchase. You approve card-backed purchases in the Envoy app. For a gift card, follow the returned app approval/payment step or pay the returned link yourself. The app step alone does not identify the funding source. Follow the terms shown in that flow.

Envoy is not yet listed in the ChatGPT or Claude directories, and its ChatGPT submission is in preparation. Until then, add Envoy as a custom connector. Read [Data and permissions](https://agent.envoy.money/docs/get-started/data-and-permissions/), [Privacy](https://envoy.money/privacy) and [Terms](https://envoy.money/terms) before connecting.

## Installation matrix

| Host | Installation and availability |
| --- | --- |
| [Grok](#grok) | Remote connector and private skills. Grok Build is separate. |

## Downloads

| Artifact | Use |
| --- | --- |
| [envoy-pay-with-envoy-0.4.15.zip](https://agent.envoy.money/downloads/envoy-pay-with-envoy-0.4.15.zip) | Individual commerce skill |
| [envoy-check-envoy-account-0.4.15.zip](https://agent.envoy.money/downloads/envoy-check-envoy-account-0.4.15.zip) | Individual read-only account skill |

Verify downloaded archives against [SHA256SUMS](https://agent.envoy.money/downloads/SHA256SUMS) before installation. [skills-release.json](https://agent.envoy.money/downloads/skills-release.json) records the current filenames, URLs, hashes, skill names, endpoint and guide URL. Only the current supported archives are distributed.

## Connection

Use this exact public **Streamable HTTP** MCP endpoint, with Envoy's existing OAuth flow:

```text
https://api.envoy.money/mcp
```

Configure `/mcp` and check the catalog for the host you connected. The default profile receives all thirteen tools: `get_account`, `list_transactions`, `list_purchases`, `start_purchase`, `get_purchase_status`, `answer_purchase_question`, `submit_answer` (its deprecated name), `report_checkout_result`, `report_checkout_step`, `cancel_purchase`, `list_gift_card_merchants`, `get_merchants` (its deprecated name) and `search_products`. A connection Envoy identifies as Claude receives nine and omits `report_checkout_result`, `report_checkout_step`, `submit_answer` and `get_merchants`. A connection Envoy identifies as ChatGPT receives eight: it also omits `list_gift_card_merchants`, and buys only from Elixir's marketplace (`search_products`, then `start_purchase` with its `product_id`). A different catalog is stale; refresh it as described in [upgrade and refresh](#upgrade-and-refresh). Complete OAuth through the host’s supported setup path. Packages contain no credentials, personal connection IDs or account state.

Open the authorization link generated by the host for this connection attempt. Complete sign-in and review the connection approval. Return to your agent and confirm that the connection is authenticated. Then call `get_account` with `{}` for a read-only check. If sign-in expires or fails, start a fresh sign-in through the host.

Do not paste OTPs, authorization codes, callback URLs containing codes, or access tokens into the conversation.

The tool catalog lists operations, not a promise that every merchant or payment service is available. Read `services` from `get_account` for account availability. Use `get_merchants` and `search_products` only for the discovery each tool supports. Follow the purchase reply for the available payment path.

When Envoy offers a gift-card payment link, the user pays that link. The agent never opens or pays it. The link task supplies the amount due, the gift-card value and the next action. Gift cards can also use an app approval or in-app payment; follow the returned task. The app step does not identify the funding source, and the app shows the actual payable before confirmation. Unused value stays on the gift card. This path does not release a one-time payment card. Its availability depends on the merchant, account and connection; it is not a way around a host restriction.

## Grok

On Grok.com, open **Connectors → New Connector → Custom**, enter the endpoint above and complete authentication if required. Connectors are available to all Grok users; Business/Enterprise administrators must first provision them. The server must be publicly reachable. [Official connector setup](https://docs.x.ai/grok/connectors), [administrator controls](https://docs.x.ai/grok/connector-management), [transport requirements](https://docs.x.ai/grok/connectors/custom-mcp-tunneling).

In Grok Bot, reuse its Envoy connector and provide the unchanged [commerce](https://agent.envoy.money/skills/pay-with-envoy/SKILL.md) and [account](https://agent.envoy.money/skills/check-envoy-account/SKILL.md) sources. Ask the Bot to save them as private skills; inspect the saved content under **Marketplace → Your plugins → Manage plugins and skills**, then verify a fresh task. [Private skills](https://docs.x.ai/grok-bot/skills-routines-and-automations), [management](https://docs.x.ai/grok-bot/settings-and-notifications).

## Upgrade and refresh

Retain the connection owner, authentication and any installation key in designated storage, plus purchase/request references and saved default. None belongs in the package.

- Verify the archive, then **replace the plugin folder, do not overlay it**; stale manifests/instructions must not survive. Refresh/reinstall through host controls and start a fresh task. Keep one copy of each supported skill.
- For Claude organization uploads, a ZIP with the same plugin name replaces the prior version. For GitHub-managed distribution, use the host's sync/update controls. Source changes alone do not prove the installed copy refreshed. [Claude updates](https://support.claude.com/en/articles/13837433-manage-plugins-for-your-organization), [OpenAI imports and sync](https://learn.chatgpt.com/docs/enterprise/plugin-management).
- **Package refresh is not tool-schema refresh.** Use connector discovery/refresh controls, then inspect a fresh task's catalog for the tools expected on that host under [Connection](#connection). ChatGPT developer-mode connections provide **Refresh**. Reconnect only for required authentication/owner/key recovery, revoked access, or an endpoint change the host cannot edit. Upgrading alone requires no reconnect. Claude connector edits require removal/re-addition. [ChatGPT refresh](https://developers.openai.com/plugins/deploy/connect-chatgpt), [Claude edits](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp).

Do not delete credentials, browser profiles, cookies, IndexedDB keys or connection records as package cleanup. Preserve unresolved purchases across updates and follow the current service recovery action; an upgrade does not start a replacement purchase.

## Removal

| Intent | Existing mechanism |
| --- | --- |
| Remove instructions | Disable/uninstall the plugin or individual skills in the host; remove only the dedicated package source when appropriate. |
| Revoke account access | Separately disconnect/revoke the Envoy connection using its supported controls. Removing skill files is not revocation. |
| Stop an active payment/card | Request `cancel_purchase` only when the current purchase permits it, and observe the returned state. If issuance has started and cancellation is refused, continue the same purchase as instructed. After a report, do not infer new cancellation or payment permission. Plugin removal or disconnection does not prove it stopped. |
| Cancel a merchant order | Use the merchant's cancellation process. Envoy card stop and merchant cancellation are separate outcomes. |

| Host | Where to remove or disable |
| --- | --- |
| Grok | Review **Marketplace → Your plugins → Manage plugins and skills** in Bot. Exact private-skill deletion UI is not publicly documented; verify removal in a fresh task. Grok.com organization administrators remove connectors through **console.x.ai → team → Grok Business → Connectors → Remove**. [Bot controls](https://docs.x.ai/grok-bot/settings-and-notifications), [admin removal](https://docs.x.ai/grok/connector-management). |

## Verify your installation

On each host you use — Grok, Claude, ChatGPT and ChatGPT Work — confirm, in a fresh task: the installed version, the host's expected catalog (thirteen tools for the default profile; nine when Envoy identifies the connection as Claude; eight for ChatGPT), that the skill is selected (explicitly invoking a skill is not the same as the host selecting it on its own), that your connected account carries over, and that a saved default is recalled.