# AiCure

> AiCure (AICure Corporation, New York) builds AI-driven patient engagement and medication-adherence
> software for clinical trials. Its H.Code platform uses smartphone computer vision to confirm dosing,
> captures audio and video for digital phenotyping, and feeds predictive analytics, ePRO and site
> dashboards for pharmaceutical sponsors, CROs and investigative sites.

Generated by API Evangelist on 2026-09-14 from AiCure's own public surface. AiCure does not publish
an llms.txt; this file is generated, not fetched. https://aicure.com/llms.txt returned HTTP 404.

## What is and is not callable

AiCure's commercial platform has **no public API**. The production host api.aicure.com is an AWS API
Gateway that answers every anonymous request - including `/`, `/openapi.json` and every
`/.well-known/*` path - with HTTP 403 `{"message":"Missing Authentication Token"}`. There is no
developer portal, no sign-up, no pricing page and no published contract for it. login.aicure.com is a
customer sign-in application. Integrations with EDC, IWRS/IRT and CRO systems are delivered as
bilateral sponsor engagements, not as a self-serve API.

AiCure's one public, machine-readable API is **OpenDBM**, the AGPL-3.0 open-source
digital-behavioral-measurement toolkit it publishes at github.com/AiCure/open_dbm. OpenDBM ships a
**self-hosted** FastAPI REST service. You run it; AiCure does not host it.

## OpenDBM REST API (self-hosted)

- Documentation: https://aicure.github.io/open_dbm/extras/odbm-rest-api
- Source: https://github.com/AiCure/open_dbm/tree/master/rest_api
- Base URL: your own host, `http://127.0.0.1:8000` in the documented local run
- Auth: OAuth2 password grant -> `Authorization: Bearer <JWT>`; no scopes
- Contract: FastAPI generates OpenAPI at runtime on your instance (`/docs`, `/redoc`). AiCure
  publishes no OpenAPI document anywhere public, so this catalog holds none.

Operations (all POST, all under `/odbm/v1`):

- `POST /odbm/v1/login` - exchange username + password for a JWT. Unauthenticated.
- `POST /odbm/v1/upload` - multipart upload of a video or audio file; returns its stored path.
- `POST /odbm/v1/video/facial` - facial activity, action units, emotional and pain expressivity, eye
  blink behavior, eye gaze directionality, facial asymmetry, facial tremor.
- `POST /odbm/v1/video/acoustic` - verbal acoustics from a video's audio track.
- `POST /odbm/v1/video/movement` - head and upper-body movement.
- `POST /odbm/v1/video/speech` - rate of speech, pause characteristics, lexical richness, parts of
  speech, sentiment of speech.
- `POST /odbm/v1/audio/acoustic` - verbal acoustics from an audio file.
- `POST /odbm/v1/audio/speech` - speech measures from an audio file.

Analysis operations take `file_url` (the path returned by upload), `platform`, and an optional
`variables` array naming biomarker variables. They are **synchronous** and return a **ZIP of CSV**,
not JSON. There is no job id, no polling and no callback.

## Conventions an agent needs to know

- Idempotency: none. No Idempotency-Key, no request-id echo. Re-uploading the same file_name
  overwrites it.
- Reversibility: none documented. Upload is the only durable write and there is no delete, undo or
  restore operation, and no stated retention window.
- Rate limits: none documented, none implemented, no RateLimit-* or Retry-After headers.
- Pagination: not applicable; no operation returns a collection.
- Errors: not RFC 9457. `{"detail": "..."}` for HTTP exceptions, `{"detail": [...]}` with 422 for
  validation failures, `{"app_exception": "...", "context": {...}}` for application exceptions.
- Versioning: `/odbm/v1`, never incremented. No deprecation policy, no Sunset headers, no status page.

## Test surface

AiCure publishes shipped demo credentials (`aicure` / `opendbm`) and a test fixture video
(`facial_speech_verbal_video_test.mp4`) so a first local run needs no setup. Both unlock only the
service you are running yourself. Details: https://aicure.github.io/open_dbm/extras/odbm-rest-api

## Currency warning

The `opendbm` package on PyPI is at **0.0.1b6, published 2022-12-20**, and the GitHub repository's
last commit is 2023-02-10. The documentation site presents versions 2.0 and 2.1 as current, and both
of its "Changelog" links (`releases/tag/v2.0.0`, `releases/tag/v2.1.0`) return HTTP 404. Installing
from PyPI gets you a 2022 beta, not the 2.1 the docs describe.

## Packages

- PyPI `opendbm` - https://pypi.org/project/opendbm/ - official, AGPL-3.0, 0.0.1b6 (2022-12-20)

No npm, RubyGems, crates.io, NuGet, Maven Central or Go module is published by AiCure.

## Agent surfaces

- MCP server: none. No hosted endpoint, no stdio package. A derived candidate tool list is recorded
  at mcp/aicure-mcp.yml purely as analysis.
- A2A agent card: none. `/.well-known/agent-card.json` and `/.well-known/agent.json` were probed on
  aicure.com, www.aicure.com, api.aicure.com and aicure.github.io. All missed.
- AsyncAPI / webhooks: none published.
- llms.txt: none published by AiCure.

## Compliance

AiCure states ISO 27001 and SOC 2 certification and HIPAA, GDPR and 21 CFR Part 11 compliance for
PHI handling: https://aicure.com/company/data-privacy-security. SOC 2 reports are restricted to
specified parties; no trust portal, certificate number or auditor is published. No security.txt and
no vulnerability disclosure programme was found on any host.

## Documentation

- OpenDBM docs home: https://aicure.github.io/open_dbm/
- Getting started: https://aicure.github.io/open_dbm/docs/getting-started
- Python API reference: https://aicure.github.io/open_dbm/api/api-doc
- Biomarker variables: https://aicure.github.io/open_dbm/docs/biomaker-variables
- Versions: https://aicure.github.io/open_dbm/versions
- Issue reporting: https://aicure.github.io/open_dbm/extras/issue-reporting
- GitHub organization: https://github.com/AiCure

## Company

- Website: https://aicure.com/
- H.Code platform: https://aicure.com/solutions/aicure-platform
- Digital phenotypes: https://aicure.com/solutions/digital-biomarkers
- Blog: https://aicure.com/blog
- Publications: https://aicure.com/resources/publications
- Contact: https://aicure.com/contact
- Terms of use: https://aicure.com/terms-of-use
- Privacy policy: https://aicure.com/privacy-policy