Skip to main content

Documentation Index

Fetch the complete documentation index at: https://sovrnti.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Sovrnti Graph follows the Resource.Action.Constraint scope naming convention. Every endpoint and MCP tool requires exactly one scope. Your client requests scopes during the OAuth flow; the consent screen at auth.sovrnti.io shows what’s being granted.
ScopeDescriptionSurfaces
Ping.ReadCall the ping endpoint and tool.GET /v1/ping, sovrnti.ping

​
Audience binding

Every issued JWT has aud=https://graph.sovrnti.io/mcp (RFC 8707). Tokens issued for one resource don’t work on another.

​
Requesting scopes

MCP clients request the scopes they need during the OAuth flow; you approve or deny per scope on the consent screen. For REST integrations using direct OAuth, include the scope parameter in your authorize URL: 
https://auth.sovrnti.io/oauth/authorize?…&scope=Ping.Read