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.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(finish): log order 029 closed with the grok connector commit and what the probe measured
nirholase05181582cff
diff --git a/prompts/finish/_context/x-grok-PROGRESS.md b/prompts/finish/_context/x-grok-PROGRESS.mdindex cabaa627d..087761cf3 100644--- a/prompts/finish/_context/x-grok-PROGRESS.md+++ b/prompts/finish/_context/x-grok-PROGRESS.md@@ -71,3 +71,9 @@ Cross-session handoff for the `x-grok-` orders ([x-grok-00-CONTEXT.md](x-grok-00- Step 0 measured: per-caller caps keyed on the ChatGPT `openai/subject` (chatgpt surface), the `Mcp-Session-Id` the grok surface issues, else the IP; 4 generations per minute and 30 per hour per caller, a 300 per hour per-IP pool cap whenever a subject keys the caps, 300 requests per minute transport per IP, a global breaker. A capped caller got a REST-shaped 429 (`error: rate_limited`) with no reset time or remedy in the message. No Grok Bot traffic in the logs yet (pre-launch), as the order expects.- Keying now: install token, then surface subject, then IP. Unknown, malformed or unreachable-DB tokens fall back to today's keying. Denials are HTTP 429 plus JSON-RPC error `-32029` with the limit, reset time and remedy (install endpoint or the OAuth server) in the message and `error.data`.- Evidence: local run against `server/index.mjs` with the real database: token A 200 x4 then 429, token B from the same IP 200, no token 200. Migration applied alone after `npm run db:status` showed it as the only pending file. Vitest 31987 pass; the one failure (`tests/onboarding-tier.test.js` lite menu size) is from another session's nav change.++## 2026-10-09: order 029 (one Grok connector URL) done++- Shipped `b025b8bb2`: `/api/mcp-grok` lists no widget templates or ui:// resources, and a caller with a valid OAuth token or connector key also gets an allowlist of account agent, memory, skill and avatar tools (`api/_mcp-studio/account-tools.js`). A tool on the financial policy tier or with a wallet, payment, trade or launch scope is never listed or callable. `?auth=oauth` on the URL forces the 401 challenge so Grok starts sign-in.+- Measured: the same surface already existed on the diverged `evolve` branch; it was ported by hand onto main (main lacks `spendScopeFor`, so value-moving detection is the policy tier plus a scope regex). Probe against a clean worktree server: all 8 servers pass, grok anonymous 14 tools, with a key 24, OAuth challenge ok. 72 tests pass across the grok, resources, probe and install suites.+- Not verified: the probe on the shared :3000 server (stale modules and another agent's unapplied `preset` migration made it fail for reasons outside this order).