Install Jentic One Beta

Connect the Bodygram Platform API to your agent

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

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%2Fbodygram.com%2Fbodygram" | sh

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%2Fbodygram.com%2Fbodygram" | 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.

Capabilities

What an agent can do with Bodygram Platform API.

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

GET STARTED

Start building with Bodygram Platform API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Bodygram Platform API for, with concrete tasks.

★ 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.

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.

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.

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.

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

12 endpoints — the bodygram platform api turns photos into body measurements for an organization.

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

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

Why Jentic?

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

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Bodygram Platform API through Jentic.

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.

Bodygram Platform API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Community OpenAPI document · agent-readyAI/MLVisionapiKey12 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For 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.

Use for: Create a body scan from a set of photos, Get the measurements for a completed scan, Adjust the measurements on an existing scan, List all scans for my organization

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

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

93%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

30%

Example Density

How richly the API is illustrated with examples.

94%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

60%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

63%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

66%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Bodygram Platform API to your agent

Capabilities

Start building with Bodygram Platform API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Bodygram Platform API

Jentic AI Readiness Score

Bodygram Platform API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness