Browse documentation
PRODUCTOverviewHow it worksTRIDENT accessAPI keys & gatewayFunding & accountingTreasury & activityFrequently asked questionsLive data & chartsAPI model profiles
BUILD & OPERATEDeploy to VercelSetup & operationsArchitectureSecurityVerificationLegacy computeOrbio researchDesign & assets
TERMS & PRIVACYTerms of servicePrivacy & pseudonymityRisk disclosuresSupport & complaintsAustralian considerations
TRIDENT PROTOCOL / DOCUMENTATION
Updated 22 September 2026 · Project-branded, wallet-based access

Historical personal compute

The legacy /api/compute endpoint is retired and returns HTTP 410, regardless of old environment flags. Use TRIDENT holder API access. Historic payment and accounting records remain available to their authenticated wallet owners for reconciliation; they do not grant inference without the current TRIDENT holding requirement and wallet limits.