# BLNG

> BLNG is an AI-driven creative suite for the jewelry industry. Its Design product turns sketches, photos or
> text prompts into photorealistic jewelry renderings on web and iOS; Studio turns CAD models into marketing
> photos and videos at scale; Retail enables live, made-to-order design in store. BLNG is a Speedinvest
> portfolio company.

This file was GENERATED by API Evangelist from BLNG's own published artifacts on 2026-08-13. BLNG does not
serve an llms.txt of its own — https://blng.ai/llms.txt and https://docs.blng.ai/llms.txt both return 404.

## What BLNG publishes for developers

BLNG runs no developer program, publishes no API documentation, no SDK and no API keys. What it does have
is three first-party REST APIs behind the web application, whose OpenAPI definitions are served publicly
and unauthenticated behind Swagger UI at the API host roots. They are not linked from blng.ai or
docs.blng.ai. They are real, they parse, and they describe 88 operations.

- Journey API — https://journeys.blng.ai/ (spec: https://journeys.blng.ai/swagger.yaml, OpenAPI 3.0.3, base https://journeys.blng.ai/v2, 33 operations)
- User API — https://users.blng.ai/ (spec: https://users.blng.ai/swagger.yaml, OpenAPI 3.0.1, base https://users.blng.ai, 47 operations)
- Billing API — https://billing.blng.ai/ (spec: https://billing.blng.ai/swagger.yaml, OpenAPI 3.0.1, base https://billing.blng.ai, 8 operations)

## Authentication

All three services authenticate with an AWS Cognito bearer JWT — an `access_token` or `id_token` issued at
https://auth.app.blng.ai. The only OAuth flow declared in the specs is `implicit`, with the scopes `email`,
`profile`, `openid` and `aws.cognito.signin.user.admin`. The User API additionally declares a
client_credentials machine token (scope `blng/billing`) used service-to-service by Billing.

Exactly one operation answers without a token: `GET https://billing.blng.ai/billing/products`, which returns
the live Stripe product and price catalog.

## Journey API — what it does

Design and shopping journeys, the prompts run against them, uploaded and generated image assets, chat
prompts (v2 and v3), multi-stage design plans, asynchronous image operations, and 3D model generation and
format conversion. Cursor pagination via `pageSize` + `nextPageKey`. Conditional GETs with `ETag` /
`If-None-Match` / 304 on four read operations. Long-running work returns 202 Accepted and is polled — there
are no callbacks. Binary assets never transit the API: uploads and downloads go through short-lived
presigned S3 URLs.

## User API — what it does

Users, roles and permissions, workspaces and workspace members, workspace invitations, per-workspace SSO
configuration, organizations, subscriptions, marketing consent (modelled as a consent receipt, not a
boolean), and onboarding tooltips. 17 of its 47 operations are marked `deprecated: true` — the entire flat
`/invitations` surface, the entire `/organizations` surface and both `/composite/*` operations. The live
model is `/users/{userId}/workspaces`.

## Billing API — what it does

Lists Stripe products and prices, creates Stripe checkout and customer-portal sessions, confirms checkout,
and submits enterprise "contact sales" inquiries. It also exposes three inbound webhook receivers that
Stripe calls. There is no consumer-subscribable event surface anywhere at BLNG.

## Runtime semantics an agent needs

- Idempotency: NOT supported. No `Idempotency-Key` on any of the 88 operations, and no `If-Match`
  precondition on any write. A retried POST is not deduplicated.
- Rate limits: no numeric limit is published and no `RateLimit-*`, `X-RateLimit-*` or `Retry-After` header
  is declared. Exceeding the per-user chat-prompt concurrency limit returns 429 with
  `{"code":"CONCURRENCY_LIMIT_EXCEEDED"}`.
- Locking: starting a 3D generation while another operation is in flight returns 423 with
  `operationInFlight`, `operationOwnerId` and `operationExpiresAt` — the only response that tells a client
  when to retry.
- Errors: not RFC 9457. Three different envelopes across three services; only one named error code exists.
- No MCP server, no A2A agent card, no `/.well-known/` document on any BLNG host.

## Plans

- Starter — free. 1 editor, 3 design files, 24 hour history, 4 artistic styles, personal non-commercial use.
- Professional — USD 49 per user per month. Unlimited design files and history, priority queue, 4K upscaling,
  3 editors, 1 team. This is the only product in the live Stripe catalog.
- Enterprise (Design) — contact sales. Unlimited teams and editors, custom AI models and styles, SSO,
  integration services.
- Retail Enterprise and Studio Enterprise — contact sales.

## Links

- Website: https://blng.ai
- Product documentation: https://docs.blng.ai/
- Getting started: https://docs.blng.ai/getting-started/
- Help center: https://portal.blng.ai/
- Pricing: https://blng.ai/pricing
- News: https://blng.ai/news
- Application / sign up: https://app.blng.ai/
- Status: https://status.blng.ai/
- Trust center: https://trust.blng.ai/
- GitHub: https://github.com/blng-ai
- Terms: https://blng.ai/terms
- Privacy: https://blng.ai/privacy-policy
- Support: support@blng.ai

## API Evangelist profile

- Provider profile: https://apis.io/providers/blng
- Artifacts: openapi/, authentication/, scopes/, conventions/, errors/, lifecycle/, data-model/,
  conformance/, rate-limits/, plans/, security/, well-known/, overlays/, mcp/, skills/, packages/