So security is part of the API contract, not an extra enterprise page. We publish only the guarantees the current system actually backs.Open the Trust CenterRead the security docs
Never hand an administrative secret to a browser or a mobile application. Use restricted credentials with exactly the scope they need.
A tenant boundary must not exist only in frontend code. AACSearch provides primitives for server-enforced access boundaries. For SaaS, that means search where each customer reaches only the data they are allowed to see.
Depending on the supported contract, a key can be restricted by:
That way a client application gets only the area of access it needs.
The availability of each capability is published separately and may depend on your plan. For example:
If AACSearch does not yet hold a particular certification, we say so plainly. If an SLA is not active yet, it must not look like it is. Trust is built on verifiable facts, not on the number of badges.
{
"scope": "search",
"allowed_collections": ["products"],
"allowed_fields": ["id", "name", "price", "image"],
"allowed_origins": ["https://shop.example.com"]
}Explore more
The best way to evaluate a search platform isn't reading one more comparison table.
Only then make the decision.