> For the complete documentation index, see [llms.txt](https://docs.superagency.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.superagency.pro/company-name-strategy.md).

# Company Name Strategy

Naming is strategic. While "AISA" is our working name, this document tracks our due diligence across available names, trademarks, and web domains — along with potential alternatives should legal conflicts arise.

It also covers how the name reflects our values: AI with Soul, Agency, Access, and Alignment. Whatever the final name, it must resonate with global audiences, remain flexible for future projects, and reflect both human creativity and technical credibility.

**AISA Pte. Ltd.**

**Artificial Intelligence Super Agency Pte. Ltd.**

**AI Super Agency Pte. Ltd.**

*Noting that a preliminary business name search has found an expiry, de-registered entry for the shortened, AISA Pte. Ltd in Singapore. We will clarify the status of this name, and consider whether it's even our top choice for expressing the vision and brand of the enterprise.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.superagency.pro/company-name-strategy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.