oneira
OverviewFeaturesCompareSpecsPreorder a Founding Unit · $80
Oneira guides/Custom APIs

Builder tutorial / custom APIs

Connect your own API without handing over the keys.

How to connect a custom API to an AI device safely: scoped credentials, read-only first, human approval for writes, and how Oneira applies your permissions.

Preorder a Founding Unit · $80 →See current features →

Product status

What is available now?

  • Working today

    Working today means the expressive face has been demonstrated on a real Oneira device.

  • Connected beta

    Connected beta features require the Oneira app, internet access, a compatible service, and permissions you approve. They can change and may not work with every service.

What you need

Connected beta features need the Oneira app, internet access, a supported service, and permissions you approve. A separate account or fee may also be required.

The short answer

Custom API connections ship on Oneira, and the design work is yours: scope a credential, start with reads, and keep a human decision in front of anything that writes. The app applies the permissions you set and routes requests only where you pointed them.

Transparent Oneira hardware study representing a device that reaches services through configured connections
Illustrative hardware study / connections explained
Custom APIsShip today
CredentialsLeast-privilege keys
First callsRead-only
WritesHuman approval

Oneira Dream Big+

A local AI powerhouse in a star.

Small enough to look playful. Built with a dual AI chip, OLED screen, and 1K camera, plus optional connected experiences you control.

Each $80 Founding Unit includes one Oneira device with a dual AI chip, OLED screen, and 1K camera, plus the selected color and included eye set. Only the final 1K camera module may change before fulfillment. Optional connected services, separate accounts, usage, and third-party fees are not included.

On-device

On-device reactions

Oneira's expressive reactions run on the device, so its face can respond without relying on a cloud request.

See how reactions work ↗
Working prototype

Dual AI chip, OLED screen, and 1K camera

The working prototype includes a dual AI chip, OLED screen, and 1K camera. The dual AI chip, OLED screen, and 1K camera are included in the $80 Founding Unit; only the final 1K camera module may change before fulfillment.

See included hardware ↗
Connected beta

Optional connected services

Optional compatible connected services can extend Oneira when you choose. Setup, permissions, internet access, service terms, accounts, usage, and fees remain separate. Connected experiences work only with compatible services the owner deliberately configures. Oneira does not connect automatically to every service.

See compatible connections ↗
Connected beta

Compatible connected tools

Compatible connected tools are optional and owner-configured. Nothing is preconfigured, and universal compatibility is not promised.

See connected features ↗
Web beta

Dream Big+ photo generation

The 1K camera supports deliberate, owner-triggered experiences. Optional Dream creation can transform a photo when the owner chooses it.

Open Oneira Create ↗
Developer preview

Focused helpers

Optional helper experiences have narrow, visible limits. Broader research, coding, and workspace actions remain in development.

Understand the agent path ↗
The honest boundary

Oneira's focused helpers have narrow, visible limits. Broader research, coding, and approved-workspace actions remain in development.

A simple flow

How it works in three steps.

  1. 01
    01 / Scope

    Pick one endpoint and one job it should do

    →
  2. 02
    02 / Credential

    Issue a dedicated key with the minimum access

    →
  3. 03
    03 / Sequence

    Prove reads first, then gate writes behind approval

The concept

A custom API connection is a doorway you define.

A custom API connection points an AI device at an interface you control — your own service, a home server, an internal tool — instead of a packaged integration someone else designed. You decide which endpoints exist, what they accept, and what they return.

That control is the appeal and the responsibility. Nothing stands between the device and your service except the boundaries you design, which is why the safety patterns below matter more here than anywhere else.

Credentials

Issue keys the way you would issue trust.

Authenticate every call, and never with a credential that can do more than the connection needs. A dedicated key with least-privilege scope means a leaked or misused credential is a contained problem instead of an account takeover.

Keep the key revocable and specific to this one connection, so you can cut an integration off without touching anything else. If your API distinguishes read scopes from write scopes, use that distinction — it is the cheapest security boundary available.

Sequencing

Reads earn trust. Writes spend it.

Start with one read-only endpoint and one small task, and confirm the round trip does what you expect before adding anything. A read that fails or returns something odd costs you nothing; it just teaches you about the connection.

Writes are different. Any call that changes state — posts, sends, deletes, purchases — should stay behind an explicit human approval, at least until the integration has a history you have reviewed. Automation can propose; you approve.

On Oneira

Your API, your accounts, your permissions.

Custom API connections ship on Oneira today, and the published pattern is the same as every connection: you configure the service, authenticate with your own accounts, and grant specific permissions in the Oneira app, which routes requests only where you pointed them.

The accounts and any fees behind your API are yours, and a service name is never an automatic live connection. Endpoint-level configuration details beyond this pattern are not published in this guide.

Sources and scope

Official facts, linked.

  • Oneira APIs and integrations — capability overview ↗

This independent comparison is not sponsored or endorsed by the compared company. Product names and trademarks belong to their respective owners.

Questions, answered

The details that decide a purchase.

What counts as a custom API here?+

Any web API you control or are authorized to use — your own service, an internal tool, a third-party API you hold a key for. The connection is custom because you define what it exposes.

Why start read-only when writes are the useful part?+

Because reads prove the whole path — authentication, routing, formatting — with nothing at stake. Once the connection has a track record, add writes one at a time behind human approval.

Can a connected request touch endpoints I did not configure?+

The app routes requests only to services you deliberately configured, with the permissions you granted. Scoping the credential itself adds a second wall on your side of the API.

Who pays for the API usage?+

You do, on your own accounts. No Oneira subscription is required for the core product; hosting, third-party API plans, and usage fees behind your connections stay yours.

Is there a list of exact configuration steps?+

This guide teaches the pattern — connect, authenticate, grant specific permissions, test small — because per-screen steps are not published here. Check current Oneira documentation when you set up a real connection.

Keep exploring

Understand the product before you choose it.

Oneira Connect / app + internetYour tools. In your pocket.→Agent guide / intent before autonomyWhat should a physical AI agent controller control?→Automation guide / one deliberate pressA physical button for the automations you trust.→

Oneira / current availability

Preorder a Founding Unit · $80

500 Drop 01 units remain across 5 currently available colors. Availability is confirmed when secure checkout begins.

Preorder a Founding Unit · $80 →
oneira

Dual AI chip. OLED screen. 1K camera.

ComparePrivacyPreorder termsSupport