THE .SI FIELD GUIDE
Agent .si domain ideas
Explore agent .si domain ideas around tools, tasks, workflows and operators. Choose names that explain the automation, then check each candidate.
Agent .si domain ideas should describe the work an agent performs and who remains in control. Names based on tasks, tools or workflows can explain a product more clearly than a generic intelligence claim. Candidates here are unverified until you run a lookup.
Ideas are not advertised as available. Check a name to retrieve its status. Counts describe combinations, not available inventory.
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Not checked
Name the task before the technology
Write down the action the agent helps with: triaging requests, coordinating research, routing work or operating a tool. A task-centered domain can remain understandable even if the underlying model changes. Choose vocabulary that your customer already uses. An operator dashboard and a consumer planning assistant need different names because their responsibilities differ. The .si suffix can provide a compact address, but the label should communicate the actual workflow rather than requiring the extension to explain everything.
Five useful agent naming patterns
Task names such as taskpilot suggest guided work. Tool names such as toolharbor suggest a place to connect capabilities. Workflow names such as workloop imply repeated coordination. Operator vocabulary can suit dashboards with clear human approval, while studio or garden vocabulary may suit environments for building agents. These associations are examples, not product facts or availability promises. Select the pattern that matches what users can actually configure, inspect and control.
Make the control boundary clear
A name containing pilot, operator or autonomous can create expectations about responsibility. Explain whether the software suggests actions, executes them after approval or runs within a defined permission set. Avoid implying that a domain ending establishes reliability or authorization. Test the name with someone outside the development team and ask what they think the agent can do. If the answer suggests more access or independence than the product has, change the name or clarify the positioning.
Check crowded automation vocabulary
Search exact phrases and related spellings before choosing familiar automation terms. A useful descriptive word may already identify another product in the same market. Compare spoken versions of agent, agenda, action and operator combinations; similar sounds can make a name difficult to distinguish in a meeting. Review relevant trademark records in your target markets. A no-record .si response does not establish that you may use the same name as an existing workflow service.
Check and compare the final candidates
Use a small set of candidates representing different task or workflow ideas. Individual and page scans query official Register.si records, with a checked time attached to each result. Save a shortlist locally and open the result details to compare registration and renewal costs. You can export checked records for a team discussion; the export is a dated observation, not a reservation. Confirm exact spelling, account ownership and any required registrant verification with the selected provider.
Primary sources
Registry rules come from Register.si. Delegation comes from IANA. Provider details come from the provider. Availability is checked separately and can change at any time.
How we verify