harness-multitool

0003 — Authentication: API keys shipped, no subscription login shipped

Decision

The project ships Auth implementations for API keys. It does not ship, and will not accept, an implementation that signs in with a model vendor's consumer subscription. The Auth interface is public; a user may write such an implementation for their own local build. Responsibility for that — including compliance with the vendor's terms — lies with the user who builds it, and the README says so.

Why

Vendors may restrict the use of consumer subscriptions outside their own clients; distributing a client that does it would put the project in that position. A public interface keeps the harness usable with whatever credentials a user is entitled to use, without the project distributing the grey part.

Note

Whether a given vendor's terms allow a user's self-built client is not something this project assesses; it is not legal advice.

This page's source