Request.
A managed user asks for model capacity beyond the current route.
◇ Sponsored
Sponsored model unlocks.
Sponsors can help managed users keep working. The unlock is labeled. The agent loop stays clean.
∠maintools4ctx28k / 200kcost$0.00modesafewaiting
How it works.
A managed user may be offered a sponsored model unlock in the Studio. The sponsor is named, the surface is labeled, and the unlock affects access only. It does not place sponsor text in code, model output, tool results, or plans.
Disclosure.
Picasso shows a clearly labeled sponsor message in the Studio.
Access.
The user can continue with the unlocked model route while the agent output remains untouched.
What never happens.
No sponsor text in output.
Generated code, model responses, tool results, and plans stay clean.
No hidden routing influence.
Sponsor relationships do not choose models, tools, memory, or subagents.
No forced path.
The user can continue on the current route when they do not want the unlock.
Frequency cap.
Sponsor unlock surfaces are capped so access support does not become the work. The Studio shows sponsor state, dismissals, and available choices.
Sponsor controls.
Users can inspect why a sponsor appears and block sponsor surfaces they do not want to see.
picasso sponsors whypicasso sponsors block <sponsor>Where it appears.
| Surface | Format | User control |
|---|---|---|
| Terminal. | One-line labeled sponsor strip. | Dismiss or hide in paranoid mode. |
| Dashboard. | Clearly labeled display placement. | Block sponsor or disable managed surfaces where allowed. |
| Unlock. | Studio-based sponsored model access offer. | Decline and continue on the current model route. |
For sponsors.
Sponsor campaigns are reviewed for developer relevance, product safety, disclosure language, frequency caps, and blocklist behavior. To start a review before launch, choose Sponsor on the waitlist and the team will reach out.