Skip to main content
Darwin Supply uses one canonical resource model across its interfaces. Choose the interface based on who is acting and which trust boundary holds the credential. No Supply CLI is planned. Python installation instructions remain unpublished while the distribution is paused.

Trust boundary

Use Supply Web for payout, ownership, credentials, archival, and other consequential human operations. Keep SDK credentials on a trusted backend. MCP uses Darwin OAuth and cannot exceed the authenticated user’s live business membership or granted scopes.