Skip to main content

​
Option 1 — add the Rings connector (fastest)

Rings is published in Perplexity’s connector directory. Nothing to configure.

Add Rings AI in Perplexity

Open the listing, connect it, and sign in with your Rings account.

​
Option 2 — add it yourself as a custom connector

Use this when you need to manage the connector under your own organization’s settings.
Custom connectors require a paid Perplexity plan. On Enterprise, admins must first enable Allow members to add custom connectors — it is off by default.
1

Open connector settings

  • For yourself: Account settings → Connectors
  • For the whole organization (admins): Enterprise settings → Permissions → Connectors permissions
2

Start a custom connector

Click + Custom connector in the top-right corner, then select Remote in the modal.
3

Fill in the fields

Leave Client ID and Client Secret empty — Rings supports dynamic client registration and OAuth discovery, so Perplexity finds the endpoints and scopes itself.
4

Acknowledge and add

Tick the acknowledgement box, then click Add. The connector appears on the Connectors screen in your account settings.
5

Authenticate

Click the Rings connector card to start the sign-in flow and enable it.
6

Turn it on for a search

On the Perplexity home screen, enable Rings under Sources.

​
Sharing it with your organization

Only admins can share a connector organization-wide. After creating it, the creator opens Enterprise settings → Permissions and shares it there. Organization members may not see it immediately. For an org-wide connector using OAuth, an admin can either authenticate once on behalf of everyone, or require each member to sign in with their own Rings account. Per-member sign-in is the right choice for Rings, because tool results are scoped to what each user can already see in the app.

​
Editing or removing it

On the Connectors screen, click the ellipsis (⋮) on the Rings card and pick the action you want.
If the connector shows an error tag right after you add it, Perplexity’s verification probe could not reach the server. Re-check the URL — it must be https:// and end in /mcp.