This morning, a question for Claude Code.
Zappa generates prompts. Our clients build them, copy them, and paste them into Higgsfield. Nano Banana Pro runs there. That’s where the image is created.
Two systems. A cut-and-paste in between.
I wanted to eliminate that cut-and-paste. But it was never possible. Higgsfield did not accept attachments — no faces, no clothing, no references. And without references, a direct link is pointless for us. Identity first, always.
So the question this morning: is it possible now?
What We Discovered
It is now possible.
Nano Banana Pro accepts reference images. Multiple per generation. Faces, clothing, accessories — all in one call. Up to 4K, all aspect ratios.
And there is something that fits perfectly with how we work: Reference Elements. You upload a face or an outfit once, and then reuse it in every prompt. A reusable library of models and clothing. This is not a gimmick. This is a foundation.
We also looked at Soul Characters. Digital twins, trained on photos. Not for us. One person per image, limited models. Elements is the way forward.
The Question Behind the Question
Higgsfield has a web app and a separate Cloud API. Programmes like Zappa communicate via that API. Through code, not through cut-and-paste.
But one thing we are still unsure about: whether Nano Banana Pro and Reference Elements are even available via that Cloud API. The public documentation is unclear. The SDK on GitHub only shows older models — Flux Pro, legacy Soul. Nano Banana Pro is nowhere to be found.
This cannot be resolved by more searching. Only by testing.
What Claude Code is Doing Now
So we are building an MVP. Small, focused, in a separate folder within the Zappa repo: experiments/higgsfield-poc/. What works, stays. What doesn’t, we discard.
Claude Code is now working on the foundations.
First, an API key, securely in a .env that never goes to GitHub. Then a test script that wants to know three things:
Three checks. A few minutes of running. After that, we will know if this entire plan can technically stand.
Along the way, Claude Code neatly followed the steps we are accustomed to. First git pull. Noticed an uncommitted change in the .gitignore and neatly stashed it before pulling. Set permissions on the .env to 600. No key in sight. No hasty steps.
That is the difference I seek. Not speed. Control.
Afterwards
Only when the three checks are green do we proceed.
Then comes the test environment in Zappa. A separate tab. Clients log into their own Higgsfield, work on their own account, generate images without leaving Zappa.
And only then do we design the interface. Not before. A mockup of something that cannot technically be done is a beautiful lie.
