We Made It to Christie’s! AI + Art + Voxta.ai
Added 2025-03-31 08:43:08 +0000 UTCHey everyone!
We’ve been keeping this under wraps for a while, but now that the dust has settled, we’re super excited to finally share something big with you. Our Voxta.ai tech was part of Christie’s first-ever AI-only art auction — Augmented Intelligence — which ran in NYC from February 20 to March 5, 2025.
We teamed up with the amazing Claire Silver, who reached out and invited us to collaborate on a project for the show. She’s an incredibly talented artist pushing the boundaries of AI and art, and it was a real honor to work with her.
Here’s what we did: we powered a Proto Hologram display with Voxta and brought a fully interactive character to life inside the box. Visitors could talk to her, she could see them, react, perform animations, and have real conversations — all powered by our tech. It was wild seeing people interact with her in real-time at such a legendary event.
This was a huge moment for us. To be a part of something this meaningful — the first ever AI-focused auction at one of the world’s most iconic art institutions — is something we’re really proud of.
Huge thanks again to Claire Silver for the opportunity and to everyone who supported us along the way. We can’t wait to show you what’s next.
– The Voxta.ai Team
NBC: https://www.nbcnews.com/now/video/christie-s-begins-ai-art-auction-amid-backlash-232929861750
Comments
try this: https://doc.voxta.ai/docs/troubleshooting-solutions/
Voxta
2025-04-13 20:06:57 +0000 UTCHi there, I'm using the latest version of Voxta and running into a consistent issue with WebView2. When I launch the app, I get this error: "System.Runtime.InteropServices.COMException (0x8007139F): The group or resource is not in the correct state to perform the requested operation." I’ve already tried the suggested fix for reinstalling or repairing WebView2, but the problem keeps coming back—especially after I start adding modules. The strange thing is, a fresh install sometimes works fine for a while, then breaks again with the same error. Is there anything else I can try? Or could this be a known issue tied to how Voxta loads modules?
RDC
2025-04-12 00:18:36 +0000 UTCOne step closer to Joi
Michael Mitchell
2025-04-08 01:41:49 +0000 UTC
