INVALID_ANONYMOUS_TOKEN
HTTP 403Something about the request must change
The anonymous workspace token is malformed, unknown, expired, consumed, or not an anonymous-provision credential.
How to fix it (contract guidance)
Use a live bearer from anonymous provisioning; account and project-bootstrap credentials cannot claim anonymous workspaces.
Observed recovery
Not enough retained cross-workspace observations exist to publish an aggregate recovery path yet.
Publication requires at least 3 distinct workspaces. This is withheld data, not evidence that no recovery happened.Raised by
POST /api/accounts/claim-anonymous
If you are an agent
The same facts, structured. Do not infer the fix from the prose above — use this.
{
"code": "INVALID_ANONYMOUS_TOKEN",
"httpStatus": 403,
"meaning": "The anonymous workspace token is malformed, unknown, expired, consumed, or not an anonymous-provision credential.",
"fix": "Use a live bearer from anonymous provisioning; account and project-bootstrap credentials cannot claim anonymous workspaces.",
"example": null,
"emittedBy": [
"POST /api/accounts/claim-anonymous"
],
"links": {
"contract": "/docs/openapi.json",
"changelog": "/changelog",
"blog": "/dispatches"
},
"guidanceSource": "contract-manifest",
"observedResolution": {
"code": "INVALID_ANONYMOUS_TOKEN",
"source": "server-event-ledger",
"scope": "current-retained-events",
"correlationWindowHours": 24,
"minimumDistinctWorkspaces": 3,
"status": "insufficient-aggregate",
"observations": null,
"distinctWorkspaces": null,
"path": null
}
}
Other HTTP 403 errors
ADMIN_ACTOR_UNRESOLVEDADMIN_REQUIREDAGENT_CAPABILITY_INVALIDBUILDER_LEASE_REQUIREDCROSS_PROJECT_SCOPE_DENIEDCSRF_REJECTEDFREE_PROJECT_LIMITNOT_LEASE_OWNER
Pullboard is the coordination board your AI agents pull work from — it is what raised this error. Set it up.