Intelligence Chat
Use ZDR-routed models, Y2 tools, and shared workspace Agent Y2 credits
Y2 Intelligence Chat combines a selectable language model with platform tools for research, documentation, news, profiles, and intelligence data. Chat is available in active Lite, Pro, and Elite workspaces.
Start a conversation
Open Chat
Select Chat in the signed-in app. Free workspaces see an upgrade wall because their chat credit limit is zero.
Select a model
Open the model selector and choose an available model. The list is populated from Y2's current ZDR-eligible catalog, so names and availability can change between visits.
Describe the outcome
Ask a direct question or use a quick action for web search, InfoOps setup, topic research, or Y2 documentation.
Review tool activity
The thread displays tool activity and structured result cards when the model searches data or proposes a profile change. Verify consequential results before confirming a write action.
Press Enter to send and Shift+Enter for a new line. While a response is streaming, use the stop control to end generation. You can change the model for an existing thread or regenerate the last assistant response.
Model routing and privacy
The selector returns only model records marked as supporting Zero Data Retention. At request time, Y2 also asks OpenRouter to deny provider data collection, require compatible request parameters, and route only to ZDR endpoints.
ZDR applies to external model routing. Y2 still stores chat threads, messages, tool results, workspace context, attachments when used, and usage records to operate the product. Tools such as web search or image generation also send the necessary prompt or query to their configured service.
If a saved model is no longer ZDR-eligible, Y2 falls back to an eligible default when one exists; otherwise thread creation or model selection fails with a model-unavailable error.
Available tools
Tools are attached to a request according to the active workspace's entitlements and the selected model's capabilities.
A zero-cost internal tool can still be part of a metered chat response. Model input and output tokens consume Agent Y2 credits even when the tool itself adds no external-service charge.
Write actions and confirmation
Some tools can change Y2 data:
- Follow a public or community profile.
- Create a custom InfoOps profile.
- Update profile settings or status.
- Start investigation enrichment.
The profile flows are designed to search the shared library first, preview proposed settings or changes, and wait for explicit confirmation before creating or updating. Read the structured card carefully, especially the profile, schedule, active workspace, and community-sharing setting.
Agent Y2 credits
One Agent Y2 credit represents $0.01 of normalized usage. The active workspace has one shared monthly pool: members, API keys, Automations, and tools do not receive separate allowances. Y2 meters model input and output using the selected model's pricing data or a fallback pricing tier when provider pricing is absent. Certain tools add usage, while internal cache reads and profile mutations currently add no separate tool charge.
| Plan | Monthly Agent Y2 allowance | Agent Y2 access |
|---|---|---|
| Free | 0 credits | No |
| Lite | 100 credits per month | Yes |
| Pro | 1,000 credits per month | Yes |
| Elite | 10,000 credits per month | Yes, with workspace governance views |
The balance reports the allowance, settled credits, active request holds, available credits, exact period boundaries, and next replenishment time. Organization governance also attributes settled usage and active holds to members and request sources without creating per-member allowances.
Billing periods
Monthly subscriptions use the active Stripe subscription boundaries. Annual subscriptions still replenish the monthly allowance each month, anchored to the UTC date and time when the annual term began. Payment cadence never multiplies the allowance. If no active paid-subscription period is available, credits use UTC calendar months.
Before provider work begins, Y2 creates a bounded, request-scoped hold. Settling converts only that request's actual cost into usage; failures release its hold; expired holds stop reducing available credits. At 80% committed usage (settled plus active holds) the UI warns, at 95% it shows a critical warning, and at 100% it disables new messages until replenishment.
Organize and remove conversations
Chat stores threads for the signed-in user and loads recent history in the sidebar. Threads can be associated with a Y2 project, renamed, switched to another eligible model, and deleted.
Deleting a thread also deletes its stored chat messages. Treat deletion as permanent and export or copy anything you need first.