canonical: https://jentic.com/apis/bodygram.com/bodygram

# Bodygram Platform API

The Bodygram Platform API turns photos into body measurements for an organization. It creates scans from submitted images, returns the resulting measurements by scan id, and lets you adjust a scan after the fact. It also issues scan tokens for client-side capture and manages the organization's API keys and account.

## For AI agents

Create body scans from photos, read the resulting measurements by scan id, adjust scans, issue capture tokens, and manage organization API keys with the Bodygram Platform API.

## Scope

Does not sell apparel, track fitness activity, or store photos beyond scanning. Use for creating Bodygram body scans and reading their measurements only.

## Capabilities

- Create body scans from photos for an organization
- Retrieve a scan and its body measurements by id
- Adjust the measurements on an existing scan
- List and delete an organization's scans
- Issue scan tokens for client-side capture sessions
- Manage an organization's API keys and account

## Use cases

### AI agent body measurement

An AI agent in an apparel or fitting workflow can turn a customer's photos into measurements on demand. Through Jentic the agent searches by intent and the API key never enters its prompt context, so a sizing assistant can create a scan and read back measurements without a hand-built integration.

Example prompt: Use Jentic to search 'create a body scan', call POST `/api/orgs/{organizationId}/scans` with the photos, then GET `/api/orgs/{organizationId}/scans/{id}` to read the measurements.

### Client capture token flow

A mobile app captures the photos on the client and needs a short-lived token to submit them. The agent issues a scan token for the organization and later lists the resulting scans, keeping capture credentials off the client's long-lived keys.

Example prompt: Issue a scan token via POST `/api/orgs/{organizationId}/scan-tokens` for a client capture session, then list results with GET `/api/orgs/{organizationId}/scans.`

### Measurement adjustment

When a measurement needs correction, an agent adjusts the scan and re-reads it. This keeps a scan's measurements accurate after review without recapturing the photos.

Example prompt: Adjust a scan's measurements via POST `/api/orgs/{organizationId}/scans/{id}/adjust` and re-read it with GET `/api/orgs/{organizationId}/scans/{id}.`

### Organization key management

An operations agent maintains the API keys an organization uses to reach Bodygram. It lists existing keys, creates a new one for a service, and revokes an old key, keeping access current across the organization's integrations.

Example prompt: List keys via GET `/api/orgs/{organizationId}/keys`, create one with POST `/api/orgs/{organizationId}/keys`, and revoke an old one with DELETE `/api/orgs/{organizationId}/keys/{id}.`

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/orgs/{organizationId}/scans` | Create a body scan |
| GET | `/api/orgs/{organizationId}/scans/{id}` | Get a scan and its measurements |
| POST | `/api/orgs/{organizationId}/scans/{id}/adjust` | Adjust scan measurements |
| GET | `/api/orgs/{organizationId}/scans` | List scans |
| POST | `/api/orgs/{organizationId}/scan-tokens` | Issue a scan token |
| GET | `/api/orgs/{organizationId}/keys` | List API keys |
| POST | `/api/orgs/{organizationId}/keys` | Create an API key |
| GET | `/api/account` | Get the organization account |

## Key resources

- **Scans** — Body scans created from photos and their measurements
- **Scan Tokens** — Short-lived tokens for client-side capture
- **Keys** — Organization API keys
- **Account** — The organization account

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 73 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 56 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 66 / 100
- **View full report:** https://jentic.com/apis/bodygram.com/bodygram/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Bodygram Platform API by hand means sending your API key in the Authorization header to platform.bodygram.com, submitting scans, and reading measurements yourself. Through Jentic you install once, import Bodygram from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Bodygram puts the organization and scan ids in the URL path (`/api/orgs/{organizationId}/scans/{id}`), so a rule can pin your agent to one organization. You choose the operations it may call, so deleting scans or the account is not included unless you add them.
- **Credential handling:** Your Bodygram API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a body scan' or 'read scan measurements', and Jentic returns the matching Bodygram operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **WeFitter** — WeFitter aggregates body and activity metrics from connected devices and apps
- **Fitbit** — Fitbit reports device-tracked body and activity data
- **1Fit** — 1Fit provides fitness and body data for health and wellness apps

## FAQ

### Is there a Bodygram Platform API MCP server?

You don't need an MCP server to give your agent Bodygram. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the scan and measurement operations. That keeps your agent's context free of an extra server's tool definitions.

### What authentication does the Bodygram Platform API use?

It authenticates with an API key sent in the Authorization header, per its OpenAPI spec. Through Jentic the key is stored encrypted by your own instance and injected at call time, so it never reaches the agent's context.

### Can I get body measurements from photos with the Bodygram Platform API?

Yes. POST `/api/orgs/{organizationId}/scans` creates a scan from submitted photos, and GET `/api/orgs/{organizationId}/scans/{id}` returns the resulting measurements for that scan.

### Can I manage API keys for my organization through this API?

Yes. GET `/api/orgs/{organizationId}/keys` lists an organization's keys, POST `/api/orgs/{organizationId}/keys` creates a new one, and DELETE `/api/orgs/{organizationId}/keys/{id}` revokes an existing key.

### How do I create a body scan through Jentic?

Search Jentic for 'create a body scan', load the input schema, and execute POST `/api/orgs/{organizationId}/scans` with the photos. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit what my agent is allowed to do with the Bodygram Platform API?

Yes. Write a rule that allows only the scan-create and scan-read operations under one organization id, so the agent can create scans and read measurements and touch nothing else, and every call it makes is logged. Deleting scans or the account stays out unless you add those operations.