ııı motion.mdVideo style specification
Higgsfield / V319

Higgsfield API | Multi-model interface

Explain the API's value through relationships: a unified entry connects to models, which connect to products. Give integration steps and pricing their own sections.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 48.42 seconds
Motion and composition example Open separately ↗
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Higgsfield API|Multi-model API · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#090a08}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="sequence"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>
Visual elementsAPI coreModel nameOutput cardPrice barStep checklistApplication connections
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Clarify the entry point and destinations first

Keep the API core at the visual center, models on one side or around it, and application outputs on another layer. Give connections clear direction and connect nodes after they appear; do not arbitrarily link unrelated objects.

A dark background, fluorescent green core, and short white labels create a technical feel. APIs and commands can use monospace, explanatory headings bold sans serif, and nodes brief names.

02

Separate capability demonstrations from pricing

Use model and output networks to explain coverage, then switch to bars or numbers sharing a baseline for pricing. Group comparison subjects, currency, billing units, and discount terms together; do not present price bars as performance bars.

03

Make integration steps readable in order

Arrange application, key acquisition, model selection, invocation, and deployment according to the actual workflow. Activate each step only after the previous one is complete, then open multiple applications around the same entry point.

04

Adapt to a new developer platform

List genuinely supported models or services first, then choose corresponding application examples. Replace API addresses, commands, access conditions, and commercial information together; retain the structure from one entry to many capabilities and outputs.

SEQUENCE

Sections and rhythm

Click a section to seek to it in the choreography example above.

Composition reference at 0.00 seconds
0.00s
Composition reference at 9.00 seconds
9.00s
Composition reference at 14.00 seconds
14.00s
Composition reference at 25.00 seconds
25.00s
Composition reference at 32.00 seconds
32.00s
Composition reference at 44.00 seconds
44.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Adapt to a multi-service platform introduction, preserving entry→capabilities→integration→applications
  • Commercial figures must use verifiable data specific to the new subject

Production constraints

API core / Model names / Output cards / Price bars / Step checklist / Application connections

  • Connect one entry point to multiple models, then connect them to multiple product outputs
  • give price comparisons and discounts their own section rather than treating price animation as a usage experience
  • check off integration steps one by one, then gather multiple instances along the connecting lines at the end