Skip to content

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.

docs(api-reference): correct the tutor endpoints and log the entry for holders

nirholase0d878251c80
diff --git a/data/changelog.json b/data/changelog.json
index 2965769d5..37b5cf8e3 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,32 @@
{
"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security. `link` is optional and must be a live three.ws path.",
"entries": [
+ {
+ "date": "2026-08-15",
+ "title": "The trades feed stopped labelling a winning exit with a losing multiple",
+ "summary": "When an agent sells part of a position to take its initial stake back and lets the rest ride, only that final sell is recorded against the position, while the profit percentage covers both sells. The feed was working out the “×” badge from the final sell alone, so a trade that returned +88% could show up as “0.56× +88%” on the same row. The multiple is now worked out from the trade's actual return, so the two numbers always agree. A coin's page also asked the feed for every trade on that coin and was quietly given only the ones above +10%, hiding the rest of that coin's history; it now gets what it asked for. The feed also answers a malformed page cursor or coin address by saying so, instead of returning results for the wrong coin, and a database problem no longer looks like a platform where nobody has ever turned a profit.",
+ "tags": [
+ "fix"
+ ],
+ "link": "/trades"
+ },
+ {
+ "date": "2026-08-15",
+ "title": "A profile’s follower count now matches the people the follower list can actually show you",
+ "summary": "The follower and following numbers on a profile counted every follow ever recorded, including ones from accounts that were later deleted or that never claimed a username. The list behind those numbers only shows people you can open a profile for, so a profile could advertise followers and then open to an empty list. Both numbers are now counted over exactly the people the list renders, so the badge and the list always agree. The list itself also stopped dropping those accounts only after it had already paged, which could hand you a blank page of followers with no way to reach the real ones behind it. Separately, the Creations tab used to answer a corrupted page cursor with a silent empty page that read as \"nothing more to load\"; it now says the cursor is malformed, and an unknown filter is rejected instead of quietly returning everything.",
+ "tags": [
+ "fix"
+ ]
+ },
+ {
+ "date": "2026-08-15",
+ "title": "The Tutor’s running tab and end-of-session invoice now show what you actually paid",
+ "summary": "The Tutor charges one cent per answer and keeps an itemized tab you can reload later and close for a signed invoice. That ledger only ever knew how to store itself in a key-value service this deployment does not run, so nothing was ever written down: reopening the page never restored your history, and ending a session always produced an invoice reading \"no questions\" and a total of zero, however many answers you had paid for. The tab is now stored in the platform’s own database, so it survives a reload, a new browser tab, and any server restart, and the invoice lists every answer with its charge and a verification hash over the line items. Closing a session twice returns the identical invoice instead of a freshly stamped one, closing a session id that was never used no longer makes that id unusable for its real owner, and if the ledger itself is ever unreachable the page says so rather than quietly reporting that you owe nothing. Asking a question still succeeds even if the ledger write fails, because a bookkeeping outage should never cost you the answer you paid for.",
+ "tags": [
+ "fix"
+ ],
+ "link": "/tutor"
+ },
{
"date": "2026-08-15",
"title": "Asking for a voice that does not exist now tells you so, instead of quietly speaking in a different one",
diff --git a/docs/api-reference.md b/docs/api-reference.md
index 8564c2b25..b9e89f746 100644
--- a/docs/api-reference.md
+++ b/docs/api-reference.md
@@ -3096,6 +3096,8 @@ DELETE /api/users/:username/follow
The social-graph edge for a public profile. GET is viewer-specific (never cached). POST and DELETE are idempotent, require a session + CSRF token, block self-follows (400), and return the same envelope as GET so one round-trip updates both the button and the counts. A genuinely new edge notifies the followed user exactly once.
+`followers_count` and `following_count` count only reachable profiles: live accounts that have claimed a username. That is exactly the set `GET /api/users/:username/follows` lists, so the number and the list always agree. The same rule applies to the `stats.followers` / `stats.following` fields on `GET /api/users/:username`.
+
**Response (all three methods)**
```json
@@ -3123,7 +3125,7 @@ GET /api/users/:username/follows
| `limit` | integer | 1..100 |
| `offset` | integer | Pagination offset |
-Each row carries `is_following` (does the signed-in viewer follow that row's user) for follow-back buttons.
+Each row carries `is_following` (does the signed-in viewer follow that row's user) for follow-back buttons. Accounts without a username are excluded in the query, not after paging, so `limit`, `offset`, and `has_more` count the same rows you receive.
---
@@ -3134,7 +3136,17 @@ GET /api/users/:username
GET /api/users/:username/creations
```
-Public profile and the cursor-paginated portfolio of forged models and saved worlds attributed to that creator. Powers `/u/:username`.
+Public profile and the cursor-paginated portfolio of forged models, saved worlds, and restyled models attributed to that creator. Powers `/u/:username`.
+
+**Query parameters (`/creations`)**
+
+| Parameter | Type | Description |
+| --------- | ------- | -------------------------------------------------------------------- |
+| `type` | string | `model`, `world`, or `restyle`. Omit for all three. Anything else 400s |
+| `before` | string | ISO 8601 cursor, echoed back as `next`. A non-date value 400s |
+| `limit` | integer | 1..48, default 24 |
+
+**Response:** `{ items: [{ id, type, title, prompt, thumbnailUrl, category, viewerUrl, createdAt }], next }`. `next` is the cursor to pass as `before` for the following page, or `null` on the last page.
---