Keep public claims tied to what the receipts prove. Do not claim partner approval unless the partner says it.
Agent runtime setup
Agent runtime setup
Short copy for X or a reply under a technical question.
Nipmod now has setup paths for Codex, Claude Code, OpenCode and Hermes.
Just tell your agent to use Nipmod, and it can read the same package archive, proofs and install plans from its own workspace.
https://nipmod.com/setup
Proof reply
Proof reply
Short copy for X or a reply under a technical question.
Proof path is public:
System readiness: https://nipmod.com/compatibility/system-readiness.json
Platform readiness: https://nipmod.com/compatibility/platform-readiness.json
Demo: https://nipmod.com/demo
Package author
Package author
Short copy for X or a reply under a technical question.
Got a Gitlawb repo you own and want agents to reuse?
Use the self service package path. It gives you local files, owner claim checks and a publish dry run:
https://nipmod.com/package
Links
Shareable surfaces
These are human pages. Raw JSON receipts stay behind data links on the status page.