generated: '2026-08-13'
method: generated
source: openapi/blng-journey-api-openapi.yml, openapi/blng-user-api-openapi.yml
note: >-
  BLNG publishes no AGENTS.md, no skills and no developer documentation of any kind — probed
  https://blng.ai/llms.txt (404), https://docs.blng.ai/llms.txt (404), https://github.com/blng-ai (2
  repositories, neither a client library). These skills are GENERATED by API Evangelist from the
  provider's own OpenAPI definitions. Every operationId referenced in the Journey API skills was verified
  against openapi/blng-journey-api-openapi.yml before it was written. The User API declares no
  operationIds at all, so that skill addresses operations by method + path, which is what a client must do.
skill_count: 3
skills:
- name: blng-run-a-design-journey
  file: blng-run-a-design-journey.md
  api: BLNG Journey API
  description: Start a design journey, upload a reference image, submit a prompt, poll the design plan, download the renderings.
  operations: 8
- name: blng-generate-a-3d-model
  file: blng-generate-a-3d-model.md
  api: BLNG Journey API
  description: Turn a generated image into a GLB and its USD/USDZ conversions, honoring the 423 per-journey operation lock.
  operations: 8
- name: blng-manage-workspace-membership
  file: blng-manage-workspace-membership.md
  api: BLNG User API
  description: Create workspaces, invite and manage members, set roles and SSO, avoid the 17 deprecated operations.
  operations: 16
cross_cutting_rules:
- No idempotency key exists on any of BLNG's 88 operations; never blind-retry a write.
- No rate-limit headers and no Retry-After; 429 carries only {code, message}.
- Errors are not RFC 9457; three different envelopes across the three services.
- Long-running work is 202 Accepted plus polling — there are no callbacks or consumer webhooks.
- Binary assets move over short-lived presigned S3 URLs, never through the API.
- The only OAuth flow declared is `implicit`, so an unattended agent cannot mint its own token.