AI and Machine Access

MathOS is designed to be readable by humans and machines. Public read-only machine surfaces expose canonical state, capabilities, specification, authority, provenance, and version. Agents may read approved state; they receive no economic authority and cannot act on any wallet.

• 01GET /.well-known/mm72-agent-contract.json — agent contract
• 02GET /api/public/mathos/specification — full MathOS specification
• 03GET /api/public/mathos/state — protocol state snapshot
• 04GET /api/public/mathos/capabilities — advertised capabilities
• 05GET /api/public/mathos/authority — authority hierarchy
• 06GET /api/public/mathos/provenance — data provenance
• 07GET /api/public/mathos/version — schema and content versions
• 08GET /api/public/mathos/health — runtime health / readiness
• 09GET /api/public/math-power/definition — Math Power definition
• 10GET /api/public/missions/state — Mission Engine state

• 01Contract (BSC, chain 56) is the token authority
• 02Mission Engine owns Mission lifecycle truth
• 03Math Power engine owns the unified score
• 04Community Task Engine owns Community Task Power
• 05Reward Pool contract owns claim authority once deployed
• 06Agents read approved state only — they hold no economic authority

• 01LIVE — approved and operational
• 02SHADOW — computed and visible but not in the operational denominator
• 03INTERNAL_TEST — allowlisted internal wallets only
• 04NOT_ACTIVE — reserved but not active (e.g. Reward Claims)
• 05PLANNED — approved intent, not yet built
• 06DEPRECATED — no longer part of the product

• 01Read protocol state
• 02Read The 72M Path
• 03Read public wallet profiles (mm72:wallet-math-profile@v1)
• 04Read Math Army data
• 05Read canonical Docs

• 01Control any wallet · sign any transaction
• 02Execute trades or claims for users
• 03Complete Daily Math or Community Tasks
• 04Modify Math Power
• 05Expose private wallet or Telegram member data
• 06Never claim the 20B reserve is funded without on-chain evidence

• 01Human — rendered Docs, home dashboard, Native Swap
• 02Machine — versioned JSON at the endpoints above
• 03Both surfaces derive from the same canonical state
• 04SHADOW capabilities are never labeled LIVE on either surface

• · Fetch /api/public/mathos/state for the current protocol snapshot
• · Cache the /.well-known/mm72-agent-contract.json to discover endpoints
• · Always check the version field before caching schema-bound responses

• Can an AI agent claim rewards on my behalf?+
• Are the endpoints stable?+
• Do machine endpoints expose private data?+
• Is there an ASK MATHOS assistant today?+
• How does an agent tell LIVE from SHADOW?+
• Are docs available in machine-readable form?+