API and integrations

There is no general public REST API today

JOEY sells metered, per-request API pricing ($0.04 per request on standard plans, $0.10 on Pro Beast, the same 2.5x ratio as the Pro Beast monthly plan), but access is provisioned by request, not self-serve: "Endpoints and docs are shared when your access is set up, so this page promises a price and a path in, not a spec that could go stale," in the product's own words. Request access from getjoey.app/api-access. If you are looking for a stable, publishable integration point that exists today, the calendar feed below is it.

Calendar feed (real, stable, live today)

JOEY publishes a read-only iCalendar (ICS) subscription feed of your own appointments. Google Calendar, Apple Calendar and Outlook all subscribe to an ICS URL natively, so one mechanism covers every platform, with no OAuth app registration and no refresh token to manage.

• GET /joey-calendar-feed/<token>.ics returns text/calendar. No Authorization header is

sent or required.

• The tenant is resolved from the token alone. There is no separate tenant or user identifier

in the request; the token is the identity.

• An unknown, malformed or revoked token returns 404 with a plain text body. It never returns an

empty-but-valid calendar, because a calendar app would render that as "no appointments" and hide the fact that the link is dead.

• This feed is read-only: events you create directly in Google, Apple or Outlook do not flow

back into JOEY.

Manage your feed (create, rotate or revoke the token) from your JOEY account settings. That management endpoint requires you to be signed in; the feed URL itself does not.

Browser extension messaging contract, at a glance

The JOEY Chrome extension (Manifest V3, currently version 0.7.2) is scoped to three hosts: app.drivecentric.com, getjoey.app, and api.maditech.group. Its content scripts read your DriveCentric conversation and prepare drafts; a separate script running on getjoey.app itself is how your dashboard knows whether the extension is installed and connected on that browser. It requests the storage, alarms, activeTab and identity browser permissions and no others. See Setup: the Chrome extension for installation, and "Your privacy" on that page for what the extension does and does not store or transmit.

This is a description of what the extension does, not a specification for building against it; its internal messaging format between content scripts and the extension's own background worker is not a published or supported external contract.