Solution setup

Sponsor developer tools without polluting output.

Keep generated code, search results, and terminal output clean while presenting sponsors in a controlled UI slot.

No-code path

Use guided setup first

Use the dashboard to block sensitive industries before any public test.

Developer path

Keep control in your backend

Use a backend route and render the decision only in non-terminal visual surfaces.

Trust boundary

What stays protected

Never insert sponsors into generated code, commands, patches, or diagnostics.

Implementation rule

Start in sandbox, then promote the same placement.

Use the Server Test Key while tuning placement and disclosure. Move to the Server Production Key only when payout details and partner readiness are complete. The request shape stays the same.

Next step

Start with the SaaS path.

Create a workspace, verify email, log in, and manage your publishable and secret keys. Assisted rollout stays available for enterprise or operator-led deployment.