When to use user-owned access

Use user-owned access when each user should own their workspace, wallet, usage, and run history.

Use user-owned access when

• users already have (or should create) their own ToolPlexer account
• users should see and pay for their own usage
• your product should not own a shared wallet
• you can keep credentials behind your backend

Avoid it when

• ToolPlexer is invisible infrastructure — use direct access
• you need custom billing or an endpoint allowlist — use a proxy
• a browser or mobile client would need to receive a long-lived API key

Current authentication model

ToolPlexer currently authenticates API calls with dashboard API keys. The safe integration pattern is:

1. User signs in to your product.
2. Your backend associates that user with their ToolPlexer key or connection.
3. Your backend sends the Bearer credential to ToolPlexer.
4. Your product returns only the result and product-specific metadata.

Do not place the key in browser JavaScript, mobile bundles, or public agent instructions. If you need a managed OAuth consent flow, contact the ToolPlexer team before implementing one so the client and scopes match the supported auth surface.