--- title: "Grok Bot and the websites that never got an API | T10" url: "https://t10.net/blog/grok-bot-portals-no-api/" description: "Grok Bot gives NH small businesses AI teammates that sign into the portals you already use. Here's where it fits, and how to set one up safely." lastmod: "2026-09-23" --- ![](https://t10.net/media/blog/2026-grok-bot-portals-no-api-hero.webp) [Back to Insights](https://t10.net/blog/) # Grok Bot and the websites that never got an API T10 Consulting August 25, 2026 5 min read Every small business in New Hampshire has at least one website it logs into every week and hates. The supplier portal where you download invoices one at a time. The scheduling site that won't talk to your calendar. The state or town website where you type the same details you typed last month. None of those sites has an API a small business can connect to. For years that meant only one option: a person, a second monitor, and a Tuesday afternoon. **That's the gap Grok Bot is aimed at.** ## What Grok Bot actually is Grok Bot is an AI agent product from SpaceXAI, in beta since August 2026. It gives a business AI teammates that work on their own cloud computer. A Bot signs into the websites and apps you already use, learns a routine by watching you do it once, and keeps working until something needs your approval. That last part matters most. **A Bot that can log into anything can also get anything wrong.** The value isn't that it clicks for you. It's that it clicks for you inside boundaries you set, and stops at the points where a person should decide. ## Three New Hampshire examples These are hypothetical, but they're the shape of work we hear about on planning calls. ### A heating and plumbing shop in Belknap County Picture a four-truck shop outside Laconia. Every week someone logs into three supplier portals, downloads the invoices, and types them into the books, checking each against the purchase order. When a line doesn't match, it gets missed about as often as it gets caught. A Bot can do the downloading and the entry, and flag anything that doesn't match the order for a person to check. **Nothing gets paid because a Bot entered it.** The office manager approves the batch. ### A physical therapy practice on the Seacoast Picture a small practice in Dover whose front desk spends hours checking appointment details across a scheduling site and a couple of payer portals, none of which connect to each other. The job is repetitive, rule-based and done entirely in a browser. This one needs more care, because patient information is involved and the product is still in beta. The sensible first job is one that doesn't touch clinical or identifying data at all, such as pulling the next day's schedule counts into an internal sheet, and proving the Bot on that before going further. Some of this work may be better served by a [custom agent](https://t10.net/services/custom-ai-agents-model-training/) built around the practice's own systems, and we'll say so when it is. ### A landscaping and snow-removal outfit in Merrimack County Picture a crew based near Concord that bids on municipal and commercial contracts. Bid notices and forms live on various public websites, and someone checks them, downloads the documents and fills in the same company details every time. A Bot can watch those sites on a schedule, gather new notices into one list and pre-fill the repeated company information. **It never submits a bid.** The owner reads the notice, decides whether to bid, and presses the button. ## How to set one up safely Our [Grok Bot setup](https://t10.net/services/grok-bot-setup/) work comes down to four boundaries. They apply whatever the business. ![A four-step flow showing how to set up a Grok Bot safely, from one narrow job to a written playbook, with a person owning every Bot.](https://t10.net/media/blog/2026-grok-bot-portals-no-api-infographic.webp) ### 1\. One narrow first job Start with one repetitive, low-risk task that happens on a website and can be checked afterwards. "Download this week's invoices from the two supplier portals and enter them" is a good first job. "Handle our back office" isn't. A narrow job is easy to show once, easy to check, and easy to stop. **If you can't describe the job in two sentences, it isn't ready for a Bot.** ### 2\. Dedicated logins with minimal access Give each Bot its own accounts, with only the access its job needs. Never hand it the owner's login or an admin account. If the supplier portal lets you create a view-only or limited user, that's the one the Bot gets. This matters more than it might seem. All of one person's Bots share a single cloud computer and its logins, so anything one Bot can reach, the others can too. We also turn local-computer access off, so a Bot works only in its cloud environment. ### 3\. Approval before anything is sent, paid, deleted or submitted Draw a line around the consequential actions. The Bot can look things up, download, fill in and draft. It stops and asks before it sends an email, makes a payment, deletes a record or submits a form. We write each approval as one plain sentence: _if the invoice total doesn't match the purchase order, the office manager must approve before it's entered._ That sentence is the rule the Bot follows and the rule the team can read. ### 4\. A written playbook Every Bot gets a short document: what it does, which accounts it can reach, when it runs, where it stops for approval, who owns it and how to turn it off. **If the person who set it up is on vacation, someone else should be able to read the playbook and stop the Bot.** ## Where a person stays in charge The theme across all three examples is the same. A Bot drafts, looks up and pre-fills. A person approves anything that touches money, commitments, customer records or judgment. We also recommend running a new Bot side by side with a person for a while, on real examples, until its results are consistently right. It's a beta product and it will change, so someone should own each Bot, review its work and adjust its instructions as things move. And some work shouldn't go to a Bot at all. If a job touches sensitive systems, needs guaranteed behaviour, or has an API worth connecting to properly, a different build is usually better. ## Finding the right first job The hard part is rarely the setup. It's knowing which of your weekly chores are website-only, which have an API, and which are really judgment calls. On a discovery call we map the workflow with [Workmap](https://t10.net/tools/workmap/), marking each system as having an API, website only or offline, and writing the approval sentence for every checkpoint. Website-only steps with clear rules are where a Bot fits best. ## A first step Make a list of every website your team logs into at least once a week to copy, download or re-type something. Pick the one where the work is most repetitive and a mistake would be caught before it cost anything: supplier invoice downloads are a common winner. That's your first Bot's job. If you'd like help picking it and setting the boundaries, [book a planning call](https://t10.net/#book). [Back to Insights](https://t10.net/blog/) ## About this post Author T10 Consulting Published Aug 25, 2026 Reading time 5 min ## Tags - new hampshire - grok bot - ai agents - small business - automation ## Related posts - [Plow Renewal Letters Before the Snow Flies](https://t10.net/blog/plow-contracts-first-storm-ai/)Sep 26, 2026 - [A Shared AI Workspace for a Small NH Business](https://t10.net/blog/shared-ai-workspace-small-nh-business/)Oct 16, 2026 - [When the Water Test Comes Back: AI for NH Well Companies](https://t10.net/blog/water-test-results-letters-nh-well-companies-ai/)Oct 12, 2026 ## Want to see where AI fits in your week? A free 30-minute planning call. Tell us how the week runs, and we'll say plainly which parts AI is good at and which it isn't. [Book a planning call](https://t10.net/#book)[More insights](https://t10.net/blog/)