> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sovrnti.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Review your profile

> Read what Sovrnti holds on your vendor, at three zoom levels: the vendor and its products, one product, one capability group.

Always call this first. It shows what Sovrnti currently holds, so a correction you send is about something that is actually there.

## Three zoom levels

| Arguments           | What comes back                                                                                                                                     |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| none                | The vendor facts and every product Sovrnti covers.                                                                                                  |
| `product`           | That product's control dimensions and aspects, at levels under the EU buyer lens, plus its capability groups and SKUs.                              |
| `product` + `group` | Each capability in the group, the product's level on it, and every feature Sovrnti has mapped there, flagged when the feature has no public source. |

The third level is the one worth your time. A feature flagged as having no public source is the cheapest thing you can fix: send one `evidence` submission with a URL.

## What you get

At the deepest zoom, each capability with the product's level on it and the features mapped there:

```json theme={null}
{
	"zoom": "group",
	"lens": "EU buyer lens, large enterprise",
	"vendor": { "vendorId": "vendor-acme", "name": "Acme", "aliases": ["Acme Corp"] },
	"group": {
		"groupId": "grp-acme-ai",
		"name": "Ai capabilities",
		"description": "Assistants embedded in the suite.",
		"capabilities": [
			{
				"capabilityId": "cap-aia-access-governance",
				"name": "Access governance",
				"description": "Who can invoke the assistant, and on what data.",
				"level": 2,
				"features": [
					{
						"featureId": "feat-acme-sso",
						"name": "SSO for the assistant",
						"availabilityStatus": "GA",
						"hasSource": false
					}
				]
			}
		]
	}
}
```

`hasSource: false` is the flag worth acting on. One `evidence` submission with a URL fixes it.

`level` is the product's level on that capability, 0 to 4, under the EU buyer lens. The anchors that define what a 2 means are not shown.

## Names, never ids

`product: "Workspace"` works. If a name is ambiguous the tool answers with candidates. Pick one and resend.

## How to use it

Ask your assistant:

```text theme={null}
Show me what Sovrnti holds on our product, then the AI capabilities group.
```

## Troubleshooting

* `builder-identity-required` — your account has no active builder identity. Claim access at [sovrnti.io/builders](https://sovrnti.io/builders).
* `insufficient-scope` — revoke the connection and reconnect; the authorization flow will re-request `Builder.Read.Self`.
* `builder-target-out-of-scope` — the name you gave resolves outside your own vendor. You can only read your own subtree.
* `builder-requires-user-token` — you connected with a machine token. Builder tools are personal (R-04); reconnect as yourself.
* `builder-target-ambiguous` — the name matched more than one thing. The error lists the candidates; pick one and resend.
* `builder-target-needs-product` — name a `product` before a `group`.
* `builder-target-needs-group` — name a `group` before a `capability`.

## See also

* [For builders](/builders/overview) — the contract, in full.
* [Send a correction](/mcp/tools/sovrnti_builder_submit) — the next step once you find something wrong.