# Higgsfield API > Higgsfield's API for generating images and video from its own models (Genjutsu, Soul, Cinema Studio) and hosted ones such as Kling, Seedance and Wan. Requests are asynchronous, with polling or webhooks, and Python and TypeScript SDKs. - Canonical: https://www.anchorterminal.com/tools/higgsfield - Markdown: https://www.anchorterminal.com/tools/higgsfield.md (~7,850 tokens) - Slim: https://www.anchorterminal.com/tools/higgsfield.min.md (~1,830 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/higgsfield.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-09 ## Overview **Grade B · 63.5/100 · rank #356 of 842 · #3 in Video generation · not agent-ready · confidence medium** ## Assessment One asynchronous API for 67 video and 17 image catalogue entries, with idempotency keys, per-second list prices public without a login, and failed or moderated jobs not charged. API inputs and outputs train Higgsfield's models unless the workspace opts out, and the docs carry no changelog. The API returns 400 at the concurrency limit, with no Retry-After. ## Facts | Field | Value | | --- | --- | | Vendor | Higgsfield Inc. (https://higgsfield.ai) | | Kind | HTTP API | | Category | Video generation (https://www.anchorterminal.com/categories/video-generation) | | Transport | HTTP | | Endpoint | `https://api.higgsfield.ai` | | Auth | API key · Self-serve. A person signs up at open.higgsfield.ai (email and password, or SSO) and creates a key ID and secret in the console. Send them as `Authorization: Key :`. The legacy `hf-api-key` and `hf-secret` headers still work. Keys belong to a workspace and carry no scopes. Some endpoints that depict a real person's face or voice can need identity or business verification under the API terms. | | Pricing | Pay per use (Pay per use) · Pay as you go from a prepaid balance, priced per second of video or per image, with list prices public at open.higgsfield.ai/pricing. No free credits or free tier were found, and no sandbox. Kling 3.0 lists from $0.084 a second and Seedance 2.5 from $0.206. A lower max-discount price is shown beside each, and a cashback scheme starts at $5,000 of spend in 30 days. Credits expire after a year (checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the API docs, the OpenAPI file, llms.txt or the pricing page (checked 2026-10-08). | | Licence | Proprietary service under the Higgsfield API Terms of Service. The Python SDK repository is Apache-2.0 and the TypeScript SDK is MIT on npm | | Packages | pypi: `higgsfield-client`; npm: `@higgsfield/client` | | Source | https://github.com/higgsfield-ai/higgsfield-client | | Docs | https://docs.higgsfield.ai/docs | | llms.txt | https://docs.higgsfield.ai/docs/llms.txt | | Last release | 2026-09-17 | | GitHub stars | 126 (as of 2026-10-08) | | npm downloads / week | 197,350 | | PyPI downloads / week | 28,142 | | Surface graded | The REST API at https://api.higgsfield.ai. A hosted MCP server at https://mcp.higgsfield.ai/mcp (OAuth) belongs to the consumer product and was not graded | | Catalogue | 84 entries per the docs, 67 video in 22 families and 17 image. Higgsfield's own Genjutsu, Cinema Studio 4.0 and Soul, plus Kling, Seedance, Wan, Happy Horse, MiniMax, LTX, PixVerse and Grok | | Request lifecycle | POST to a model endpoint returns `request_id`, `status_url` and `cancel_url`. States are `queued`, `in_progress`, `completed`, `failed`, `nsfw` and `canceled` | | Max clip length | Up to 30 seconds on Seedance 2.5, Wan 3.0, Cinema Studio 4.0 and Genjutsu, 15 seconds on Kling 3.0, per the console's model cards | | Resolution | 480p to 1080p on most models, 2K on MiniMax H3, 4K on Kling 3.0 4K, Seedance 2.0 and LTX 2.5 Fast | | Audio | Optional generated audio on Kling 3.0, Seedance 2.5, Wan 3.0, LTX 2.5 and others, per the model cards | | Rate limits | Concurrency by funds added in the past 28 days. 2 for a new account, 10 from $25, 20 from $100, 40 from $1,000. Over the limit returns 400, with no `Retry-After` | | Webhooks | `hf_webhook` query parameter on submit. Retries on network failure and 5xx for up to two hours, duplicates possible, no signature documented | | Billing | Prepaid balance, credits expire after one year. `failed` and `nsfw` requests aren't charged. Invoicing under a committed-use contract | | Data use | API inputs and outputs may train Higgsfield's models unless the workspace turns the setting off. Content sent to a partner model goes to that third party | | Retention | Media files kept at least seven days. Request records kept while the account is active. Zero retention only under an enterprise addendum | | SDKs | Python `higgsfield-client` 0.2.0 (Apache-2.0 repository) and TypeScript `@higgsfield/client` 0.2.6 (MIT), both released 17 September 2026 | | Status | status.higgsfield.ai on Instatus, two components (API, Cloud Console), no notices from August to October 2026 | | Capabilities | video.generate, video.image-to-video, video.edit, video.audio, image.generate, image.edit | | Tags | official, hosted, closed-source, model-platform, card-required, openapi, llms-txt, async-jobs, webhooks, idempotency, python, typescript, status-page | | JSON | https://www.anchorterminal.com/api/v1/tools/higgsfield.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 85 | 17.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 69 | 11.2 | | Agent ergonomics | 13% | 16.2 | 77 | 12.5 | | Security & auth | 14% | 17.5 | 48 | 8.4 | | Payments & pricing | 10% | 12.5 | 20 | 2.5 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 75 | 6.6 | | Transparency & trust (editorial 45, provenance 77) | 7% | 8.8 | 61 | 5.3 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **63.5 → B** | ### Why each score - Reliability 85: Hosted reading. status.higgsfield.ai on Instatus with API and Cloud Console components and a notice history (20). No notices from August to October 2026 and 100.0 per cent shown for both components (30). Concurrency limits are published with numbers, 2 for a new account and 10, 20 and 40 at $25, $100 and $1,000 of funds added in 28 days (15). The docs give backoff with jitter, a retry table and idempotency keys for submissions, but reaching the limit returns 400 and no `Retry-After` or rate-limit headers are sent (10 of 15). The API terms say self-serve customers get no uptime commitment and an SLA exists only under an order form, with none published (0). No beta or preview label on the API (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 69: `/docs/openapi.json` is public OpenAPI 3.1 but covers 8 paths, and llms.txt calls it supplementary. Each model page carries its own full JSON Schema (15 of 25). llms.txt, llms-full.txt and Markdown twins of every page (10). Model pages state the endpoint, usage notes and limits, with little on when to pick one model over another (14 of 20). Schemas have enums, length and item limits, required fields and `additionalProperties: false` (14 of 15). cURL, Python and TypeScript examples on each page and a status-code table, but errors are a FastAPI `detail` string with no machine codes (11 of 15). Endpoints carry a version segment, and no changelog was found in the docs or sitemap (5 of 15). - Agent ergonomics 77: Submissions return a small JSON handle, results are URLs, and webhooks replace polling (20 of 25). Resolution, duration and aspect ratio set output size per model. No endpoint to list requests was found in the docs (10 of 20). The error page says which statuses to retry, but the concurrency limit arrives as a 400 with a message string and the docs warn against parsing messages (12 of 20). `Idempotency-Key` on every generation endpoint, with a 422 on a reused key with different parameters, plus cancel for queued requests (20). Few required parameters, sensible defaults, and official Python and TypeScript SDKs (15). - Security & auth 48: Hosted reading. A key ID and secret pair created and managed in the console, scoped to a workspace, with rotation advised and no permission scopes. Secrets travel in a header, not the URL (20). No read-only or restricted keys and no confirmation step. Organisations have admin and member roles, and an estimate call shows cost before spending (3 of 20). The API returns generated media and no third-party text (10). Request history and usage analytics in the console and an `X-Correlation-ID` on every response, no audit log found (8 of 15). A valid security.txt with a PGP key, expiring 12 September 2027, and a disclosure clause in the terms. No bug bounty found. The trust centre at trust.higgsfield.ai is drawn by script and was unread, so certifications are unchecked (7 of 20). No webhook signature is documented. - Payments & pricing 20: No x402, MPP or L402 (0). Per-second and per-image list prices for each model are public at open.higgsfield.ai/pricing without a login (20). No free credits or card-free trial were found. A new account gets sign-up discounts and 2 concurrent generations, and usage draws on a prepaid balance (0). A person signs up in a browser and creates the key in the console (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 75: The docs sitemap shows pages changed on 7 October 2026, and the SDKs were last released on 17 September 2026 (30). `@higgsfield/client` 0.2.4 and 0.2.6 and `higgsfield-client` 0.2.0 all shipped in September 2026 (20). No public changelog. Support is by Discord and email, and the SDK repositories have 5 and 14 open issues whose replies we couldn't read (6 of 15 for a closed service). Official Python and TypeScript SDKs are current (15). The TypeScript repository has a publish workflow and the Python one has tests but no CI workflow (4 of 10). - Transparency & trust 61: Closed service with API terms dated 2 September 2026 that are specific on licence, resale and outputs. SDKs are MIT and Apache-2.0 (15). The API terms state training on inputs and outputs by default with a workspace opt-out, request records kept while the account is active, media kept at least seven days and zero retention only by enterprise addendum. The privacy policy agrees on training. The DPA the terms incorporate was not found (20 of 30). The terms promise commercially reasonable efforts to announce model removals through a changelog, no changelog or dated notice was found, and legacy endpoints are labelled in the docs (5 of 20). Partner models are named by vendor in the catalogue. The subprocessor list is said to sit in the trust centre, which was unread, and no data locations were found (5 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (19 items): https://www.anchorterminal.com/fixes/higgsfield.md (JSON https://www.anchorterminal.com/fixes/higgsfield.json) ### What we couldn't check - unchecked: trust.higgsfield.ai is drawn by script, so certifications, the subprocessor list and security practices were unread - unchecked: the FAQ answers on open.higgsfield.ai/pricing (launch discount, agent use, spending controls) load by script, so the conditions for the max-discount prices weren't read - unchecked: the DPA that the API terms incorporate. No public link to it was found - unchecked: reply times on the SDK repositories' open issues (5 on higgsfield-client, 14 on higgsfield-js) - Whether a new account receives any free credits, and whether a card is needed before a first call. Neither was stated on the pages read - The API terms say requests over the concurrency limit are queued or rejected with a retryable error, and the docs say the API returns 400 - The API terms mention a changelog, test keys that run in dry-run mode and a `/v1/` version prefix. None of the three was found in the docs - The lead named the vendor Higgsfield AI. The legal entity in the terms is Higgsfield Inc. The rest of the lead held ### Sources - API docs index and llms.txt: (seen 2026-10-08) - full docs text (authentication, errors, idempotency, polling, rate limits, billing, webhooks, model pages): (seen 2026-10-08) - OpenAPI file: (seen 2026-10-08) - docs sitemap (page dates, no changelog page): (seen 2026-10-08) - pricing and concurrency limits: (seen 2026-10-08) - model catalogue with prices: (seen 2026-10-08) - cashback scheme: (seen 2026-10-08) - API Terms of Service, 2 September 2026: (seen 2026-10-08) - Terms of Use Agreement, 26 July 2026 (section 11, developer terms): (seen 2026-10-08) - privacy policy, 26 July 2026: (seen 2026-10-08) - status page and notice history: (seen 2026-10-08) - security.txt: (seen 2026-10-08) - trust centre (script-drawn, unread): (seen 2026-10-08) - MCP page: (seen 2026-10-08) - npm registry, @higgsfield/client: (seen 2026-10-08) - PyPI, higgsfield-client: (seen 2026-10-08) - Python SDK repository: (seen 2026-10-08) - TypeScript SDK repository: (seen 2026-10-08) - RDAP for higgsfield.ai: (seen 2026-10-08) ## Who's behind it (provenance 77/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Higgsfield Inc. | 20/20 | | Domain age | higgsfield.ai, registered 2023-06-07 (3 years) | 7/15 | | Endpoint on the vendor's domain | api.higgsfield.ai | 15/15 | | Terms of service | read, states 6 of the 7 things a reader expects, and has 1 clause that costs points | 7.1/10 | | Privacy policy | read, states 8 of the 8 things a reader expects, and has 1 clause that costs points | 8/10 | | Status page | status.higgsfield.ai | 10/10 | | Changelog | not found | 0/10 | | security.txt | valid | 10/10 | The API Terms of Service (last updated 2 September 2026) name Higgsfield Inc., 535 Mission St, 14th Floor, San Francisco, CA 94105, and are supplemental to the Terms of Use Agreement of 26 July 2026 at https://higgsfield.ai/terms-of-use-agreement. The privacy policy (last updated 26 July 2026, effective 27 August 2026) says it covers the website, applications and APIs. The API terms incorporate a DPA where Higgsfield processes personal data on a customer's behalf. We found no public link to it. The API answers at https://api.higgsfield.ai and the console at https://open.higgsfield.ai (console.higgsfield.ai redirects there). https://higgsfield.ai/.well-known/security.txt has a contact, a PGP key and an expiry of 12 September 2027. Its comment block is a set of instructions addressed to AI agents and automated security tools about testing scope. We recorded it and did not act on it. No changelog page is in the docs sitemap. The API terms list a changelog as part of the documentation. RDAP for higgsfield.ai gives a registration date of 2023-06-07. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://open.higgsfield.ai/terms-of-service), read 2026-10-08, dated 2026-09-02, states 6 of the 7 things a reader expects. - To know. Says it may use customer content to train or improve models, and gives an opt-out. "Notwithstanding Section 4.4 of the Terms of Use, for Inputs submitted to and Outputs generated by the API Service: Company may use such content to train, develop, and improve its AI models and related technology unless you opt out." - To know. Restricts benchmarking or competitive use (costs points). "You shall not use the API Service or any Output to train, fine-tune, distill, or otherwise develop or improve any artificial intelligence model that competes with the API Service or any Model" - To know. Says access can be ended without notice or for any reason. "Company may suspend your access to the API Service immediately and without prior notice where reasonably necessary to address a breach of Section 4, 6, or 8 of these API Terms, a security risk, legal or regulatory exposure, upstream provider requirements, or non-payment." - To know. Requires arbitration or waives class actions. "SECTION 18 OF THE TERMS OF USE (ARBITRATION AGREEMENT) GOVERNS HOW DISPUTES UNDER THESE API TERMS ARE RESOLVED, INCLUDING ITS MANDATORY BINDING ARBITRATION PROVISIONS, CLASS ACTION AND JURY TRIAL WAIVER, AND THIRTY (30) DAY RIGHT TO OPT OUT." - Gives the date it was last updated. Last updated 2026-09-02. - Not found in the text. Says how changes to the terms are announced. - Also in the text (2026-10-08). Content submitted to a model run by a third-party partner is transferred to that third party. "You acknowledge that Your Content submitted to a Partner Model (or to any third-party Model accessed via a third party’s API) will be transferred to that third party." - Also in the text (2026-10-08). Generated media files are kept for at least seven days, after which Higgsfield may delete them permanently. "Generated media files are available for at least seven (7) days from generation, but Company may permanently delete media files after that period." - Also in the text (2026-10-08). Prepaid units bought for API use expire one year after purchase. "Purchased Units expire one year after purchase." **Privacy policy** (https://higgsfield.ai/privacy-policy), read 2026-10-08, dated 2026-07-26, states 8 of the 8 things a reader expects. - To know. Says it may use customer content to train or improve models, and no opt-out was found (costs points). "…multimedia data, query and prompt data, and Inputs and Outputs (each as defined in our Terms of Use) to train and improve our (and our affiliates') AI models and algorithms, and for content moderation and safety purposes), improve the rest of our business, help us understand user activity on the Service, including whi…" - To know. Says it sells personal data or shares it for advertising. "We, our service providers, and our advertising partners use cookies and similar technologies to collect online activity and device data in order to deliver advertising tailored to your interests and to measure its effectiveness, including by sharing this information with advertising partners." - Gives the date it was last updated. Last updated 2026-07-26. - Says how long data is kept. For as long as needed, with no period named. - Gives a privacy contact. privacy@higgsfield.ai. - Says where data is transferred or stored. Relies on standard contractual clauses. - Also in the text (2026-10-08). The policy says use of content for model training can be stopped going forward by deleting the content or the account. "You can stop this going forward by deleting your content or account; see the 'Delete your content or account' section below." - Also in the text (2026-10-08). Content already used in trained models cannot be removed from them after deletion, and deleted content is not used for later training. "Content already incorporated into our AI models before deletion cannot feasibly be removed from models that are already trained; going forward, we will not use deleted content to train our AI models, as described in our Terms of Use." ## Live (updated 2026-10-09 09:26 UTC) - Right now: up, HTTP 405, 128 ms, checked 2026-10-09 09:26 UTC (get on `https://api.higgsfield.ai`) - Uptime 24h 100.0% (20 probes) · 30 days 100.0% (20 probes) · p50 158 ms · p95 264 ms - Vendor status page: unknown, no machine-readable status found - Always current: https://www.anchorterminal.com/api/v1/live/higgsfield.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Kling 3.0, list price from | $0.084 | per second of video | The pricing page also shows a max-discount price from $0.042. The discount's conditions weren't readable | | Seedance 2.5, list price from | $0.206 | per second of video | Max-discount price from $0.144 | | Wan 3.0 Prime, list price from | $0.068 | per second of video | Max-discount price from $0.041 | | Genjutsu 480p, list price | $0.318 | per second of video | Per second of source video, rounded up. 720p $0.681 and 1080p $1.632 per the docs. Max-discount price from $0.159 | | Kling 2.5, list price from | $0.042 | per second of video | Max-discount price from $0.021 | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Per-second list prices for each model on open.higgsfield.ai/pricing without a login, and an `/estimate/...` call that returns the cost before submitting - `Idempotency-Key` on every generation endpoint, with replays returning the original `request_id` and no second charge - Requests ending `failed` or `nsfw` aren't charged, and a queued request cancelled before it starts is refunded - Each model page carries a full JSON Schema with enums, limits and `additionalProperties: false`, and llms.txt and Markdown twins exist - status.higgsfield.ai shows no notices and 100.0 per cent for the API from August to October 2026 ## Weaknesses - API inputs and outputs can train Higgsfield's models by default. The opt-out is a workspace setting, processed within 10 business days - Reaching the concurrency limit returns `400 Bad Request` with a message string, and the docs say no rate-limit headers or `Retry-After` are sent - No changelog was found in the docs, although the API terms name one as the channel for deprecations and removals - Keys have no scopes or read-only mode, and no webhook signature is documented - No free credits were found, and a new account starts at 2 concurrent generations until it adds $25 - `/docs/openapi.json` covers 8 paths of an 84-entry catalogue, and llms.txt calls it supplementary ## Before you call it (notes for agents) 1. Send `Authorization: Key :` to https://api.higgsfield.ai. A Bearer token is rejected 2. Send a fresh `Idempotency-Key` with every generation. After a timeout or 5xx, repeat the same request with the same key, then read `status_url` 3. Treat a 400 whose `detail` mentions concurrent requests as a limit, not a bad request. Wait for a running job to finish before submitting more 4. Poll `status_url` from 2 seconds up to 10 with jitter, and stop on `completed`, `failed`, `nsfw` or `canceled` 5. Download output within seven days. Media files may be deleted after that 6. Read the model's own docs page for its schema. The OpenAPI file lists only a few models ## Connect Install: ```bash pip install higgsfield-client ``` First request: ```bash curl --request POST \ --url https://api.higgsfield.ai/higgsfield/genjutsu/motion-transfer/v1.0 \ --header "Authorization: Key ${HF_API_KEY_ID}:${HF_API_KEY_SECRET}" \ --header "Content-Type: application/json" \ --data '{"video_url": "https://example.com/input.mp4", "image_urls": ["https://example.com/input.jpg"]}' ``` Through letme (picks today, calling later): https://letme.dev/higgsfield. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | fal video models | B | 68.9 | 192 | video.generate, video.image-to-video, video.edit, video.audio | no | https://www.anchorterminal.com/tools/fal-video.md | | Alibaba Wan (Model Studio) | B | 65.1 | 300 | video.generate, video.image-to-video, video.edit, video.audio | no | https://www.anchorterminal.com/tools/alibaba-wan.md | | Replicate video models | B | 62.1 | 402 | video.generate, video.image-to-video, video.audio, video.edit | no | https://www.anchorterminal.com/tools/replicate-video.md | | Runway API | C | 60.8 | 443 | video.generate, video.image-to-video, video.edit, video.audio | no | https://www.anchorterminal.com/tools/runway.md | | MiniMax Video API | C | 60 | 482 | video.generate, video.image-to-video, video.edit, video.audio | no | https://www.anchorterminal.com/tools/minimax-video.md | | Pika API | D | 47.3 | 742 | video.generate, video.image-to-video, video.edit, video.audio | no | https://www.anchorterminal.com/tools/pika.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The docs catalogue lists 84 entries, 67 video and 17 image, across 22 video model families (source: ) - API inputs and outputs may be used to train Higgsfield's models unless the workspace turns off the training setting, which takes up to 10 business days to apply (source: ) - Content sent to a partner model is transferred to the third party that hosts it, and the training opt-out doesn't apply to models marked excluded (source: ) - Concurrency is 2 for a new account and rises to 10, 20 and 40 at $25, $100 and $1,000 of funds added in the past 28 days (source: ) - The docs say the API sends no rate-limit headers or `Retry-After`, and returns 400 when the concurrency limit is reached (source: ) - The API terms give no uptime commitment to self-serve customers. An SLA is available only under an order form (source: ) - The security.txt file ends with a comment block of instructions addressed to AI agents and automated security tools. We recorded it as a fact and did not act on it (source: ) - llms.txt tells agents to treat the OpenAPI file as supplementary and to read each model's own page for its schema (source: ) ## Compare - [Alibaba Wan (Model Studio) vs Higgsfield API](https://www.anchorterminal.com/compare/alibaba-wan-vs-higgsfield.md): B 65.1 vs B 63.5 - [fal video models vs Higgsfield API](https://www.anchorterminal.com/compare/fal-video-vs-higgsfield.md): B 68.9 vs B 63.5 - [Google Veo vs Higgsfield API](https://www.anchorterminal.com/compare/google-veo-vs-higgsfield.md): C 60.4 vs B 63.5 - [Higgsfield API vs Kling AI API](https://www.anchorterminal.com/compare/higgsfield-vs-kling.md): B 63.5 vs F 21.7 - [Higgsfield API vs Luma AI API](https://www.anchorterminal.com/compare/higgsfield-vs-luma.md): B 63.5 vs D 48.2 - [Higgsfield API vs MiniMax Video API](https://www.anchorterminal.com/compare/higgsfield-vs-minimax-video.md): B 63.5 vs C 60 - [Higgsfield API vs OpenAI Sora API](https://www.anchorterminal.com/compare/higgsfield-vs-openai-sora.md): B 63.5 vs F 9.4 - [Higgsfield API vs Pika API](https://www.anchorterminal.com/compare/higgsfield-vs-pika.md): B 63.5 vs D 47.3 - [Higgsfield API vs PixVerse API](https://www.anchorterminal.com/compare/higgsfield-vs-pixverse.md): B 63.5 vs E 42.4 - [Higgsfield API vs Replicate video models](https://www.anchorterminal.com/compare/higgsfield-vs-replicate-video.md): B 63.5 vs B 62.1 - [Higgsfield API vs Runway API](https://www.anchorterminal.com/compare/higgsfield-vs-runway.md): B 63.5 vs C 60.8 - [Higgsfield API vs Vidu API](https://www.anchorterminal.com/compare/higgsfield-vs-vidu.md): B 63.5 vs E 40.2 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on higgsfield.ai or one of its subdomains, or the README of github.com/higgsfield-ai/higgsfield-client. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "higgsfield", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Higgsfield API on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Higgsfield API on Anchor Terminal](https://www.anchorterminal.com/badges/higgsfield.svg)](https://www.anchorterminal.com/tools/higgsfield) ``` Plain link: ```html Higgsfield API on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Higgsfield API is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/higgsfield-dark.png - Light: https://www.anchorterminal.com/assets/share/higgsfield-light.png