> ## Documentation Index > Fetch the complete documentation index at: https://docs.bland.ai/llms.txt > Use this file to discover all available pages before exploring further. # Grok Bot > Let Grok Bot pay for and set up its own Bland account in one conversation, or configure the connection yourself with an existing API key. [Grok Bot](https://x.ai/bot) works from a cloud computer, can use connected tools, and can approve a payment through its own agent wallet. That combination lets it sign up for Bland, pay for its own number, and hand you the finished connection without you ever opening a signup page. Relaying a one-time code by text is your only manual step. Setting up a different assistant? See [Personal AI Agents](/integrations/mcp/personal-agents). ## Prerequisites * Access to Grok Bot with Stripe Link connected and the Link CLI available to it, to let it set itself up. The payment is a shared payment token from the CLI, not a virtual card. * Or: a Bland API key from the [dashboard](https://app.bland.ai/dashboard/settings) and a custom MCP connection that accepts a URL and headers, to configure the connection yourself * Either way, an active [Agent Phone Plan](/platform/agent-phone-plan) gets you a dedicated number and texting; headless self-setup pays for the first month as part of signup ## Option 1: Let Grok Bot set itself up **A Link virtual card is not accepted.** `/complete` takes two payment credentials: a shared payment token (`spt_`) from the Link CLI, or the Link CLI answering the payment challenge that `/complete` returns. Grok Bot's default Link tool, `request_virtual_card`, mints a virtual card, which `/complete` refuses. If Grok Bot can only get a virtual card, it can't finish headless: it has to show you the browser link from the response and let you open it. It must not open that link itself; the page is for the human owner and has a bot check. Tell Grok Bot: ```text theme={null} Read https://docs.bland.ai/integrations/mcp/grok-bot and set up a new Bland account for me with headless onboarding. Use my phone number and email, and send client_name "grok". Before you start, ask me which US area code I want for my phone number, and send it as area_code. If I say any, leave it out. Pay for the Agent Phone Plan with a Link shared payment token through the Link CLI, never a virtual card. Ask me for the SMS code, and show me any link instead of opening it. When you have the API key, add it as a custom MCP connection and confirm it works by listing my pathways. ``` To start on free credits instead, replace the second line with: "Don't pay for anything. Ask me for the SMS code, and show me any link instead of opening it." The account then calls from a shared Bland number right away, and when you ask Grok Bot for texting or its own number it shows you a link where you add a card and start the plan (see [Adding the plan later](/platform/agent-headless-onboarding#adding-the-plan-later)). If a wallet payment is declined, Grok Bot falls back to that same link. A verification code arrives at your phone by text. Relay it back to Grok Bot. On the paid path it then asks you to approve the first month of the Agent Phone Plan in the Link app, and it finishes with its API key and a phone number in the same conversation. ### What Grok Bot does The paid path is four requests and one Link approval. [Headless agent onboarding](/platform/agent-headless-onboarding) has the full request and response shapes, and [Paying with an agent wallet](/platform/agent-headless-onboarding#paying-with-an-agent-wallet) is the detailed payment reference. `POST /v1/agent/onboarding/headless/start` with your phone, your email, `client_name: "grok"`, `payment_intent: "shared_payment_token"`, and the area code you asked for as `area_code`. A 6-digit code is texted to your phone. Your number is only ever bought in that area code. If it has no numbers right now, `/start` answers `409 AREA_CODE_UNAVAILABLE` before any text is sent, and Grok Bot asks you for another area code or whether any US number is fine. Grok Bot asks you for the code. `POST /v1/agent/onboarding/headless/complete` with the session, the code, and `payment: { "request_challenge": true }`. This verifies the code, keeps the session alive, and answers `402 PLAN_REQUIRED` with a `WWW-Authenticate: Payment` header. The header carries the amount, the currency, and the Stripe network profile id of the seller. Grok Bot reads those values from the challenge, not from a doc: the price comes from the plan catalog and can change. At the time of writing the challenge names `profile_61VOTHaCdbmfq6PD5A6VOTHa3XSQ3zOF0yDybvQ6S1k8` and `1499` `usd`. The amount comes from the payment challenge and changes when the offer does. Both need `link-cli auth login` once, which you approve in the Link app. **Preferred:** `npx @stripe/link-cli mpp pay` with the same `/complete` request. The CLI reads the challenge, asks you to approve the amount in Link, and retries `/complete` with the credential. The `200` carries the API key. ```bash theme={null} npx @stripe/link-cli mpp pay https://api.bland.ai/v1/agent/onboarding/headless/complete \ -X POST \ -d '{"headless_session": "Xk9pQ2mZ...", "otp_code": "482913", "payment": {"request_challenge": true}}' \ --header "Content-Type: application/json" \ --context "First month of the Bland Agent Phone Plan for : a dedicated US phone number the agent calls and texts from, billed monthly." ``` **Manual:** decode the challenge with `link-cli mpp decode`, mint a shared payment token with `link-cli spend-request create` using the `network_id` and amount it prints (see [Mint the token with Stripe Link](/platform/agent-headless-onboarding#mint-the-token-with-stripe-link)), then repeat `/complete` with `payment: { "shared_payment_token": "spt_..." }` in place of `request_challenge`. [`GET /v1/me`](/api-v1/get/me) with the returned `api_key`, then add the key as a custom MCP connection (the values are under Option 2). The headless session lasts 10 minutes from `/start`, and the code check in step 3 restarts that window once. A re-issued challenge doesn't restart it again, so your Link approval has to land inside it. If the session expires, Grok Bot starts over with a new code. ## Option 2: Configure the connection yourself The documented Plugins flow does not establish how to add an arbitrary MCP URL with an Authorization header. Confirm that your version supports both before following the configuration below. Configure the connection with these values: | Field | Value | | - | - | | Server URL | `https://api.bland.ai/v1/mcp` | | Header name | `Authorization` | | Header value | `Bearer YOUR_BLAND_API_KEY` | Replace `YOUR_BLAND_API_KEY` with your key in the connection's credential field. Attach the connection to your task, then ask Grok Bot to list your Bland pathways to check authentication before placing a call. If the required custom-server or header controls are unavailable, use a client with documented setup, such as [Poke](/integrations/mcp/poke) or [OpenClaw](/integrations/mcp/openclaw). You can create the account yourself in the [dashboard](https://app.bland.ai) rather than through Option 1, and add the [Agent Phone Plan](/platform/agent-phone-plan) at [Billing & Plans](https://app.bland.ai/dashboard/pay?tab=plan) if you want a dedicated number and texting; without it, your agent calls from a shared Bland number on the org's free credits. On the Agent Phone Plan, calls and texts are limited to US and Canadian numbers, one call at a time, up to 60 minutes per outbound call, and up to 100 texts a day. See [Limits](/platform/agent-phone-plan#limits). ## Next steps The full request and response shapes behind Option 1, including error handling and buying credits. Two-way texting, troubleshooting, and connection requirements. Docs for agents: [llms.txt](/llms.txt) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.