Product

How Jentic Works

From API assessment to production deployment in four simple steps.

Product Overview

PLATFORM

Jentic OneSelf-hosted, open-source control plane between your agents and any APIAPI DirectoryBrowse 10,000+ APIs ready for AI agent integrationAPI ScorecardAssess your APIs for AI-readiness with automated scoringAgentic SandboxSafely simulate AI agents with your production APIsJenticSign in to the Jentic web app

CAPABILITIES

IntegrationConnect AI agents to your existing systemsWorkflowsDiscover and capture successful agent workflowsGovernanceDefine, observe, and enforce AI policies

TOOLS

Arazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually
Pricing
Developers

GET STARTED

DocumentationGuides and API referenceQuickstartGet up and running in minutes

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
Resources
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Install Jentic OneBook a Demo
How Jentic WorksJentic OneAPI DirectoryAPI ScorecardAgentic SandboxJenticIntegrationWorkflowsGovernanceArazzo UIArazzo Editor
Pricing
DocumentationQuickstartGitHubOpen Standards
Resources
About UsCareersContact
Request a demoInstall Jentic One
Jentic
For Enterprises
  • Product Overview
  • Agentic Sandbox
  • Book a Demo
For Developers
  • Jentic One
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic. All rights reserved.
APIs / Analytics / RescueTime
RescueTime logo

RescueTime APIs for AI Agents

AnalyticsWeb AnalyticsAuthenticationOfficial Vendor SpecsapiKey, oauth2Agent Ready

www.rescuetime.com·Developer portal → www.rescuetime.com

For Agents

APIs2 in catalogue
Endpoints20 indexed
AuthapiKey, oauth2 — 1 credential for all 2 APIs
ProvenanceOfficial OpenAPI specs

An agent can read RescueTime activity and productivity data, pull daily summary, alerts, highlights, and focus-session feeds, and write back highlights, offline time entries, and FocusTime start or end events across the vendor's two analytic APIs.

RescueTime records passive time-tracking data at the application and website level rather than event or product analytics, so its feeds report where attention actually went during the day. Both APIs read from the same account, differing mainly in endpoint paths and which write operations they expose.

Use for: Reading RescueTime time-tracking and productivity data, pulling daily summary, alerts, and highlight feeds, and logging highlights, offline time, and FocusTime sessions for a connected account

Not supported: payment processing, team messaging, crm records, calendar scheduling, real-time streaming

Credentials: Both APIs authenticate the same way, using an API key or OAuth2 against the same RescueTime account, so one set of credentials covers both.

All 2 RescueTime OpenAPI specs are vendor-official and indexed by Jentic, kept validated and agent-ready.

RescueTime is a time-tracking and productivity service that measures how time is spent across applications, websites, and offline activities. Its APIs expose that recorded data as analytic feeds and daily summaries, along with operations for logging highlights, posting offline time, and starting or ending FocusTime sessions. Both APIs cover the same RescueTime account data, so an agent can read productivity metrics and write focus and highlight events against a single connected account.

Jentic One on Github

RescueTime API Catalog

2 APIs across 2 product groups. All share one credential.

Analytics1

RescueTime APIProgrammatically retrieve analytic data, retrieve daily summary feed.~12 endpoints

Identity Auth1

RescueTime Analytic Data APIProgrammatically get analytic data, daily summary feed.~8 endpoints

Which RescueTime API should I use?

I want to...UseWhy
Read analytic data plus manage FocusTime sessions with explicit start and endRescueTime APIThis API exposes both start and end focus-session operations and a focus-session start events feed, so an agent can open and close a session and observe start events.
Read analytic data and log offline timeRescueTime Analytic Data APIThis API adds a post offline time operation for recording activity that happened away from tracked devices, which the other API does not expose.

Install Jentic One Beta

Connect the RescueTime APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RescueTime APIs, 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.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frescuetime.com" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frescuetime.com" | 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.

Once connected, ask your agent something like: “read RescueTime productivity data and log focus sessions”.

What AI Agents Can Do with RescueTime

Each workflow spans multiple RescueTime APIs. Jentic routes each operation to the right API automatically.

Daily productivity report with focus context

Pull the daily summary and analytic data to build a productivity report, then read the focus-session feed to annotate which blocks were tracked focus time.

Example prompt:

Call the daily summary and analytic data endpoints, then read the focus-session feed and combine both into a report.

APIs used

RescueTime API + RescueTime Analytic Data API

Log a focus block and record its offline follow-up

Start a FocusTime session through one API, then use the other to post offline time for work done away from the device during the same period.

Example prompt:

Start a FocusTime session on one API and post an offline time entry on the other for the same interval.

APIs used

RescueTime API + RescueTime Analytic Data API

Highlight and alert digest

Read the alerts and highlights feeds for the account and post new highlights to record notable events, using whichever API exposes the needed write path.

Example prompt:

Read the alerts and highlights feeds, then post a new highlight summarizing the period.

APIs used

RescueTime API + RescueTime Analytic Data API

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Setup

Wiring RescueTime by hand means choosing between its query-string API key and the OAuth2 authorization-code flow and constructing feed calls against the www.rescuetime.com host for each API. With Jentic One installed, your agent finds and adds either RescueTime API from the Jentic directory and stores the credential once.

Permission scoping

Permission scoping

Both APIs address their data through operations rather than resource ids in the path, so you scope the agent to the operations it should use. Read feeds such as daily summary or analytic data can be allowed while write operations like posting offline time or starting FocusTime stay out unless you add them, using your own rules in your Jentic One instance.

Credential management

Credential isolation

Your RescueTime API key or OAuth credentials are stored once, encrypted, in your own Jentic One instance and injected at execution time. Because one credential covers both APIs, it is entered once and never enters the agent's prompt, logs, or context.

Intent-based discovery

Intent-based discovery

Agents search the Jentic directory by intent, such as retrieving analytic data or starting a focus session, and Jentic returns the matching RescueTime operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using RescueTime APIs through Jentic.

What can an agent do across the RescueTime APIs?

An agent can read time-tracking and productivity data, pull daily summary, alerts, highlights, and focus-session feeds, and write highlights, offline time, and FocusTime start or end events. Together the two APIs cover both reading recorded activity and logging new events.

Do the two RescueTime APIs cover the same data?

Yes. Both read from the same RescueTime account and expose overlapping analytic feeds and daily summaries. They differ mainly in endpoint paths and which write operations they include, so the choice usually comes down to whether you need offline-time posting or explicit focus-session start and end.

Do I need separate credentials for each API?

No. Both APIs use the same API key or OAuth2 credentials against the same account, so one credential covers both. When connected through Jentic, that credential is stored once in your own Jentic One instance.

How fresh is the data these APIs return?

RescueTime syncs activity data roughly every 3 minutes on paid plans and every 30 minutes on the free Lite plan, so feed responses reflect near-recent activity rather than a live stream. Plan behavior is set by RescueTime, not by the API.

Which API should an agent choose for focus tracking?

Use the RescueTime API when you need to both start and end a focus session and read focus start events. Use the Analytic Data API when you additionally need to post offline time. Both read analytic data, so overlap on read operations is expected.

What are these APIs not suited for?

They cover time-tracking analytics and focus logging only. They do not handle payments, messaging, CRM records, or calendar scheduling. Despite one being tagged under authentication, neither is an identity provider; both operate on RescueTime productivity data.

If you need a different Analytics vendor

All 3 are in the Jentic catalogue with the same one-credential, intent-search pattern.

TogglTime-tracking service with an API for logging and reporting time entries, an alternative source of productivity data.
ClockifyTime-tracking API covering entries and reports, adjacent for teams comparing productivity tooling.
MixpanelProduct analytics API for event and behavior data, complementary when combining usage analytics with time tracking.

BOOK A DEMO

Start Connecting APIs to Your AI Agents

Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.

Book a Demo