Developers / Early direction
Build capability.
Preserve responsibility.
Third-party capabilities can expand what Tony understands and can do—without dissolving authority, context, or accountability.
Build for Tony
More than another
integration layer.
A capability should enter a relationship with clear purpose: what it can perceive, what it may change, who authorized it, and how its outcome is observed.
Governed capability integration
Every extension needs
a legible boundary.
The developer model is being shaped around explicit contracts of responsibility rather than silent access or unlimited automation.
- 01Declare
Purpose
Explain the capability and the conditions it needs.
- 02Request
Authority
Ask only for access relevant to the intention.
- 03Return
Observation
Make outcomes visible so Tony can close the loop.
SDK / Direction
A foundation is being
designed, not documented.
Public SDK documentation and production APIs are not available yet. The intended direction is a clear capability model, responsible permissions, testable states, and observable outcomes.
Marketplace
Capability should be
discoverable and trusted.
A future marketplace may help people discover governed capabilities for Tony. Participation, review, distribution, and commercial terms are still being defined.
Developer interest
Join the early conversation.
Tell us what you build and where governed intelligence could extend its usefulness.
Register Developer Interest