Setup & costs · Buyer guide
o1 connections, setup and service costs
The hardware does not include an AI provider account or usage. A connected o1 workflow starts with a supported service you configure, including its permissions and costs.
Start with the job, then check the connection
“I want o1 to work with my tools” becomes a useful buying question when you name one job and the service it needs. The published connection details describe compatible agents, providers, apps, APIs and automations configured by the owner. The current connected-tool description also includes supported MCP servers. These are optional connected betas, not a promise of compatibility with any account or service.
Write the job in one sentence: what should the tool read, what should it produce, and should it be allowed to change anything? Then check whether the current supported beta covers that exact workflow. If support is not confirmed, keep it as a question for the team rather than treating a familiar logo or category name as a completed integration.
Separate the device from the services
| Part of the setup | Current public position | Your next check |
|---|---|---|
| o1 hardware | Planned one-time purchase with no o1 subscription. | Final price, included features and purchase terms. |
| AI provider account and usage | Not bundled with the hardware. | Your provider’s required account and current fees. |
| Third-party agents and tools | Owner-configured examples; not included or maintained by o1. | Compatibility, setup and the service’s terms. |
| Connectivity | Internet is required for connected beta examples. | The connection and any setup device required for that beta. |
The planned lack of an o1 subscription is not a promise that every connected experience is free. There is no published universal total for third-party usage. Check the actual services you select and the final hardware offer before deciding what your setup will cost.
What the listed examples mean
The current o1 page shows Hermes Agent, Claude Code and OpenClaw as connected-beta examples. It also shows OpenAI and Anthropic under provider-backed betas, with experience labels attached to those examples. These names identify examples to investigate; they do not supply you with an account, usage allowance or a blanket compatibility guarantee.
The same page states that third-party agents are not included or maintained by o1, and that marks do not imply partnership or endorsement. Availability can depend on the supported service and owner setup. Ask for the current instructions for the example you want to use, including which parts run in a browser or another environment and which interaction belongs to the physical device.
Check these five things before enabling a tool
- Supported experience. Confirm the specific beta and task are currently supported, rather than relying on a general “apps” or “AI” label.
- Your account. Identify the account you need and whether your current access supports the required service. Hardware ownership does not create that account.
- Permissions. Review the credentials, requested access and allowed actions. A task that reads information and one that changes it may need different access.
- Connection and setup. Follow the supported instructions for internet access and any required phone or other setup environment. Do not infer a universal pairing method from the hardware render.
- Fees and exit. Check the service’s charges and how to stop the workflow or revoke access in that service. Keep the provider’s account controls available.
This is a preparation checklist, not an installation procedure. The public o1 materials say availability and setup details will be announced before sales open. Use the instructions published for the actual supported beta when you configure it.
Know what the tool can see and do
Connected tools begin only after the owner configures compatible services, credentials, permissions and allowed actions. For Sight, the stated interaction is deliberate capture of one frame used with a compatible connected service. Ask which information leaves the device and what the receiving service does with it before using a feature with private material.
The website privacy notice explicitly leaves device inputs and third-party credentials to feature-specific explanations. It does not establish that all connected features keep information locally. If offline behavior is a priority, the offline guide explains the working local reactions separately from service-backed tasks.
Make a small, reviewable setup plan
Keep your plan to one confirmed beta first. Record the service, the owner account required, the allowed task and where you will review its fees. Leave unannounced usage allowances or future integrations out of the budget. You can expand the plan once the supported workflow and its costs are clear.
For hardware availability, the Founders purchase plan and later online drops have different terms. The buying and support guide explains those paths without treating free entry as a free device. To hear when availability and final details change, join the o1 waitlist. Signing up is free and only requests launch and availability emails.