Skip to main content
Increase your app’s retention with context seeding.
Mio derives user context from email and calendar, enabling AI apps to personalise their experience from the very first interaction.

​
What is Mio?

Mio is a context layer for AI apps. It gives developers access to user preferences, letting them build truly personal experiences. For the user, it’s a simple sign in with Google at onboarding. For developers, it’s a tool call.
Mio spans three surfaces: a browser client that drives OAuth, a server runtime that secures tokens, and React helpers that plug Mio Context into your UI.

​
How the integration works

  1. Connect: start OAuth from your client experience and redirect users to the Mio dashboard.
  2. Exchange: hand the authorization code to your backend so it can store refreshToken securely and mint fresh access tokens.
  3. Get Mio Context: send getContext or getContextSummary requests with a valid accessToken to retrieve rich, ready-to-use context you can feed into any assistant, email, or workflow.

​
Quickstart

Get Started with Mio in <10 mins.

​
Why Mio?

  • Simple integration: add Mio to your app, chatbot and agent to make it personal in <10 mins.
  • Context seeding: Mio derives preferences from existing datasources during onboarding. With Mio, users get answers from an assistant that already knows them from the first time they use your app.
  • Focus on your product: instead of spending months building your own context engine and integrating datasources, plug in Mio to make your AI app personal today.

​
Get started & stay up to date

  • Need guidance fast? Read the Overview to see responsibilities by layer before you start coding.
  • Building today? Follow the Quickstart end to end, then explore the API reference for every parameter and response.
  • Want updates? Join the waitlist from the navbar, book a call, or reach out to art@mio.xyz.

​
Next up

1

Complete the quickstart

Install @mio-xyz/sdk, register your OAuth client, and confirm the browser ↔ server loop works locally.
2

Map responsibilities

Use the overview to decide when to run token refreshes, how to persist user state, and where to surface Mio Context in your product.
3

Go deep with the API reference

Each method documents required params, expected responses, and common failure modes with ready-to-copy snippets.