For Agents
Read a user's Habitify habits, log completions for a given date, and attach notes about progress or context.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Habitify 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 | shStep 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 instanceJentic 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.
What an agent can do with Habitify API.
List all habits configured in a Habitify account
Retrieve a single habit by id with its schedule and metadata
Log a habit as completed, skipped, or failed for a specified date
Update or delete an existing habit log entry
GET STARTED
Use for: List all habits in the user's Habitify account, Get the habit with id 'morning-meditation' from Habitify, Log the 'drink water' habit as completed for today, Find all logs for the 'reading' habit in the last seven days
Not supported: Does not handle gamification rewards, social challenges, or calendar scheduling - use for personal habit, log, and note management in Habitify only.
Jentic publishes the only available OpenAPI specification for Habitify API, keeping it validated and agent-ready. Habitify is a habit-tracking app for iOS, Android, web, and watch platforms. The API exposes endpoints to read habits, log completions, and manage notes attached to each habit. Agents can pull a user's habit list, mark a habit complete for a given date, and append free-text notes to track context, mood, or progress.
Attach text notes to a habit and read note history
Update or delete notes by note id
Patterns agents use Habitify API for, with concrete tasks.
★ Voice-Driven Habit Logging
Build a voice agent that logs habits as the user speaks them out loud. The agent maps an utterance like 'I just meditated' to the matching habit id and posts a log entry to /logs/{habit_id} with today's date and a completed status. Habitify handles streaks, scheduling, and multi-device sync. Setup runs in under an hour with a Habitify API key.
Find the habit named 'Meditation' and POST a log to /logs/{habit_id} with status 'completed' and today's date.
Contextual Note Capture
Capture context for each habit completion - mood, location, or a quick reflection - by writing to the habit's notes endpoint. The agent observes a completion event and posts a note via /notes/{habit_id} so the user later sees rich context in their Habitify journal. Useful for therapy support agents, journaling workflows, and ADHD coaches.
POST a note to /notes/{habit_id} for the 'morning-walk' habit with the text 'Walked along the river, mood improved noticeably.'
Cross-App Habit Sync
Mirror habits between Habitify and another tracker by listing habits via GET /habits and recreating them in the destination system. The agent pulls the source list, normalises the schedule fields, and writes equivalents downstream. Suitable for users migrating between apps or running parallel trackers.
GET /habits, list each habit's id and name, and create a matching task in a downstream productivity tool.
Agent Discovery Through Jentic
Agents search Jentic with intents like 'log a habit' and receive the Habitify operation that satisfies it, with a typed input schema. The agent loads the schema, fills in habit_id and date, and executes through the Jentic SDK. Credentials live in the Jentic vault, never in the agent prompt.
Use Jentic search 'log a habit' to find the Habitify log operation and execute it for habit_id 'reading' with status 'completed'.
10 endpoints — jentic publishes the only available openapi specification for habitify api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/habits
List all habits in the account
/habits/{habit_id}
Get a habit by id
/logs/{habit_id}
Log a completion, skip, or failure for a habit
/logs/{habit_id}/{log_id}
Delete a habit log entry
/notes/{habit_id}
Attach a note to a habit
/notes/{habit_id}/{note_id}
Delete a habit note
/habits
List all habits in the account
/habits/{habit_id}
Get a habit by id
/logs/{habit_id}
Log a completion, skip, or failure for a habit
/logs/{habit_id}/{log_id}
Delete a habit log entry
/notes/{habit_id}
Attach a note to a habit
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Habitify Authorization header API key is stored encrypted in the Jentic vault. Agents receive scoped access tokens at execution time and never see the raw key.
Intent-based discovery
Agents search Jentic with phrases like 'log a habit' or 'list habits' and receive the matching Habitify operations with their input schemas. The agent fills in habit_id and date and executes without reading docs.
Time to first call
Direct Habitify integration: a few hours to handle auth, log payload shapes, and date semantics. Through Jentic: under fifteen minutes to search, load, and execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using Habitify API through Jentic.
Why is there no official OpenAPI spec for Habitify API?
Habitify does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Habitify 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 Habitify API use?
Habitify uses an API key passed in the Authorization header. The key is generated from the Habitify account settings under integrations. Through Jentic, the key is stored encrypted in the vault and injected at execution time so the agent never receives it directly.
Can I log a habit for a past date through the Habitify API?
Yes. POST /logs/{habit_id} accepts a target date, so an agent can backfill missed completions or correct entries for previous days. Use PUT /logs/{habit_id}/{log_id} to update an existing log instead of creating a duplicate.
What endpoints are available for managing habit notes?
The /notes/{habit_id} endpoint creates and lists notes for a habit, and /notes/{habit_id}/{note_id} updates or deletes a specific note. Notes are free-text and can store mood, location, or any context the agent wants to attach to a habit completion.
How do I log a habit through Jentic?
Run pip install jentic, then search 'log a habit' in the Jentic SDK to find the Habitify POST /logs/{habit_id} operation. Load the schema, fill in habit_id, target_date, and status, and execute. The full flow takes under five minutes.
Are there rate limits on the Habitify API?
Habitify enforces a per-account rate limit on the API key. Specific quotas are not published in the spec; agents should respect 429 responses by backing off and retrying with exponential delay.
/notes/{habit_id}/{note_id}
Delete a habit note