Developers
V1MeCapture consent

Agree once to photo analysis by the disclosed AI processor

Stores the acceptance with the notice version, a policy fingerprint (recipients, routing, retention) and a timestamp. A version or policy that is no longer current returns 409 capture_consent_stale. Idempotent while the same notice is current. Saving readings still needs separate review and health-storage confirmation.

PUT
/v1/me/capture-consent

Authorization

bearer
AuthorizationBearer <token>

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X PUT "https://example.com/v1/me/capture-consent" \  -H "Content-Type: application/json" \  -d '{    "accepted": true,    "version": "2026-09-09",    "policyId": "string"  }'
{  "available": true,  "current": {    "version": "2026-09-09",    "policyId": "string"  },  "granted": true,  "grantedAt": "2019-08-24T14:15:22Z",  "stale": true}

Your one-time photo-analysis consent status GET

Photo analysis requires a stored consent that matches the current notice version and processor policy. `granted` is true only then; `stale` means an earlier consent no longer applies and the member must be asked again.

Analyse a photo into an unsaved review draft POST

Requires the member's stored one-time photo-analysis consent for the current notice version and processor policy (409 capture_consent_required otherwise); a per-request consent object is ignored for personal records. Only JPEG/PNG base64 is accepted, up to 4 MiB encoded image bytes and 16 megapixels. The advertised notice identifies the configured recipient: a private self-hosted health service, or explicitly enabled OpenRouter with Azure (US). Auto detects food/BP/glucose in one call and requires consent for all three. Identified meter photos are retained encrypted for up to 30 days; food photos are never persisted. Reuse captureId and identical input after network failure; an existing processing receipt never creates a second provider call. Unsupported, mixed, ambiguous or unreadable results require a retake. Identity documents and lab reports are not supported.