Exist.io API

Name: Exist.io API
Brand: Exist.io API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsProduct Analyticsbearer14 EndpointsREST

For Agents

Read a user's aggregated personal analytics data from Exist.io, surface insights and correlations, and write back values for owned attributes such as mood, productivity, or custom metrics.

Install Jentic One Beta

Connect the Exist.io API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Exist.io API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Exist.io API.

Read a user's aggregated daily attribute values across mood, sleep, activity, and productivity metrics

Fetch generated insights and trend correlations Exist computes from the user's tracked data

Acquire ownership of an attribute so an integration can write daily values to it

GET STARTED

Start building with Exist.io API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Exist.io API, keeping it validated and agent-ready. Exist.io is a personal analytics platform that aggregates self-tracking data from services like Fitbit, Apple Health, Oura, RescueTime, and Google Fit into one timeline. The API exposes user profiles, attribute templates, attribute values, daily insights, correlations, and averages, and lets approved clients write data to attributes they own. It is built around 14 endpoints under /api/2/ and uses bearer token authentication for personal-access or OAuth-issued tokens.

Use Cases

Patterns agents use Exist.io API for, with concrete tasks.

★ Personal Analytics Dashboard Sync

Pull a user's Exist.io profile, attribute values, and insights into a personal dashboard or journaling app. The /api/2/attributes/with-values endpoint returns combined metadata and recent values in a single call, while /api/2/insights surfaces narrative insights Exist has generated. Useful for quantified-self apps that want a unified view of mood, sleep, activity, and custom metrics without integrating each underlying source separately.

Call GET /api/2/attributes/with-values to fetch the user's last 30 days of mood, sleep, and step values, then call GET /api/2/insights to retrieve any insights generated this week.

Custom Habit Tracking Integration

Acquire ownership of a custom attribute through /api/2/attributes/acquire and write daily values back via /api/2/attributes/update or /api/2/attributes/increment. This lets a habit tracker, journaling app, or smart-home integration contribute new data into the user's Exist timeline so it can be correlated with the rest of their tracked metrics.

Call POST /api/2/attributes/acquire to claim a meditation_minutes attribute, then call POST /api/2/attributes/update with today's value of 20 minutes.

Correlation and Insight Extraction

Use /api/2/correlations and /api/2/correlations/combo to surface statistically significant relationships Exist has detected between attributes, such as caffeine intake versus sleep score. Combined with /api/2/averages, this powers reflection prompts or weekly review summaries in a coaching agent.

Call GET /api/2/correlations to list the user's strongest correlations and pick the top three to summarise in a weekly review email.

AI Reflection Agent via Jentic

An AI coaching agent loads Exist.io operations through Jentic, then on each weekly schedule pulls attribute values, insights, and correlations to draft a personalised reflection. Through Jentic the agent searches by intent ("read my exist.io insights") and receives the right operation schema, with bearer credentials kept in the Jentic vault rather than embedded in the agent.

Through Jentic, search 'read exist.io attribute values', load the GET /api/2/attributes/with-values operation, execute it for the past seven days, and summarise mood and sleep trends.

Key Endpoints

14 endpoints — jentic publishes the only available openapi specification for exist.

METHOD

PATH

DESCRIPTION

GET

/api/2/accounts/profile

Get the authenticated user's profile

GET

/api/2/attributes/with-values

List attributes with recent values

GET

/api/2/insights

Get generated insights

GET

/api/2/correlations

List discovered correlations

POST

/api/2/attributes/acquire

Acquire an attribute for writing

POST

/api/2/attributes/update

Update values on owned attributes

POST

/api/2/attributes/increment

Increment values on owned attributes

GET

/api/2/accounts/profile

Get the authenticated user's profile

GET

/api/2/attributes/with-values

List attributes with recent values

GET

/api/2/insights

Get generated insights

GET

/api/2/correlations

List discovered correlations

POST

/api/2/attributes/acquire

Acquire an attribute for writing

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Exist.io bearer tokens are stored encrypted in the Jentic vault. Agents receive a scoped, short-lived credential at execution time and the raw token never enters the agent's prompt or memory.

Intent-based discovery

Agents search Jentic by intent (e.g., 'read exist.io insights' or 'update an exist attribute') and receive the matching Exist.io operation with its input schema, so the agent calls the right endpoint without browsing developer.exist.io.

Time to first call

Direct Exist.io integration: 1-2 days for OAuth setup, attribute ownership flow, and error handling. Through Jentic: under 30 minutes — search, load, execute.

FAQs

Specific to using Exist.io API through Jentic.

Why is there no official OpenAPI spec for Exist.io API?

Exist.io does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Exist.io API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Exist.io API use?

The Exist.io API uses HTTP bearer token authentication. You pass an Authorization: Bearer <token> header where the token is either a personal access token or an OAuth2-issued token. Through Jentic the token is held in the encrypted vault and only scoped credentials are issued to the agent at execution time, so the raw token never enters agent context.

Can I write data into a user's Exist.io account with this API?

Yes, but only for attributes your client owns. Call POST /api/2/attributes/acquire to claim ownership of a custom or supported attribute, then use POST /api/2/attributes/update or POST /api/2/attributes/increment to write daily values. Attributes already owned by another integration cannot be written until they are released.

What insights and correlations are available?

GET /api/2/insights returns the narrative insights Exist generates, GET /api/2/correlations returns the strongest detected attribute pairs with their correlation strength, and GET /api/2/correlations/combo lets you query a specific pair. GET /api/2/averages returns rolling averages for an attribute.

How do I read a user's mood values for the last week through Jentic?

Run pip install jentic, then use the async client to search 'read exist.io attribute values', load the returned GET /api/2/attributes/with-values operation, and execute with attributes=mood and limit=7. Jentic returns the parsed response with no manual auth handling required.

What are the rate limits for the Exist.io API?

The OpenAPI spec does not declare rate limits. Exist.io applies per-user limits in production; treat 429 responses as authoritative and back off using the Retry-After header when present.

Exist.io API

Connect the Exist.io API to your agent

Capabilities

Start building with Exist.io API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs