Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
Quicknode startup spotlight ask
Target: Quicknode Startup Program
Program page: https://www.quicknode.com/startup (the pipeline's /startup-program URL also returns
200; the program text quoted below was read from /startup on 2026-09-16)
Verified intake: the program contact from the 2026-07 acceptance. The repo records acceptance and
approved credits (docs/listings.md) but no contact name or email. If none
exists in the owner's inbox, the public routes are https://www.quicknode.com/contact-us and the
Quicknode Discord.
What the program publicly offers that fits: "Join Feature Fridays to showcase your solutions",
"Present your vision at our events to an influential audience", and "partnership stages, from
Marketplace to Developer Relations" (program page, 2026-09-16). There is no published spotlight
application form.
Deadline: none published. Pipeline target 2026-10-09.
Owner's one step: reply in the existing Quicknode Startup Program thread with the email below and
attach the field note.
The email
Subject: Feature Friday idea: what running Quicknode as a Solana failover reserve taught us
Hi [program contact first name],
three.ws joined the Quicknode Startup Program in July. We run a multi-provider Solana RPC failover chain in production for AI agent wallets, balance reads, and payment verification, and Quicknode is the metered reserve at the end of it.
We wrote up what we learned in one page, attached: why dedupe order silently turned our reserve into our primary until 2026-07-28, how long to bench a lane for each failure class, why a 403 is not always a bad key, and why breakers have to be fleet-wide. It includes what is still hard, not just what worked.
Would the team consider it for a Feature Friday or a founder spotlight? We can present live, turn it into a co-authored post for your blog, or both. Two dates that work for us: Friday 2026-10-16 or Friday 2026-10-23. Code and docs are public: https://github.com/nirholas/three.ws and https://three.ws/docs/solana.
Thanks, [Owner name] three.ws
Fill the two bracketed names from the real thread before sending; neither is recorded in the repo.
Packet fields
One-sentence pitch: a startup-program member with a candid production write-up of running Quicknode inside a multi-provider Solana failover chain.
100-word abstract: three.ws runs AI agent wallets, balance reads, and payment verification on Solana, and routes every server-side RPC call through one priority-ordered failover chain with a Quicknode endpoint as the metered reserve. The field note covers four production lessons: dedupe order turned the reserve into the primary until July 28 and exhausted its daily cap; lanes are benched from 30 seconds to 6 hours by failure class; a call-shape 403 now demotes one method instead of a whole lane; and cooldowns are shared across the Cloud Run fleet. It closes with what failover cannot fix: capacity, the conversation this spotlight would start.
Working link: https://three.ws/docs/solana (200 on 2026-09-16)
Screenshot: images/docs-solana-failover.png, captured 2026-09-16. Alt text: "three.ws Solana docs explaining never to name the same endpoint as both primary and reserve, followed by the cooldown table for failing RPC endpoints."
Founder bio: not recorded in the repo; add two lines under the signature if Quicknode asks.
Two proposed dates: Friday 2026-10-16 or Friday 2026-10-23 (proposals, nothing booked).
Requested action: consider three.ws for a Feature Friday session or a founder spotlight, with the field note as the technical basis.
Approved relationship wording (from docs/partners.md and
docs/listings.md): three.ws is a member of the Quicknode Startup Program,
accepted 2026-07, with approved infrastructure credits. Quicknode is a rung in the Solana RPC
failover chain, not the whole chain. The /partners "Infrastructure" chip is a grouping three.ws
chose, not a Quicknode tier. Quicknode styles its own name "Quicknode" on its site.
Metrics used
| Metric | Value | Source | Captured |
|---|---|---|---|
| Program status | Accepted 2026-07, credits approved | docs/listings.md | repo |
| Quicknode position in production chain | Reserve (SOLANA_RPC_LAST_RESORT_URLS) |
Cloud Run service env, host name only | 2026-09-16 |
| RPC lane health at capture | 3 of 3 paid lanes and 9 of 9 lanes cooling | https://three.ws/api/healthz |
2026-09-16T16:01Z |
| RPC request volume through Quicknode | Not measured here. Quicknode's own dashboard is the source; the repo keeps no per-lane request count | n/a | n/a |