Overview Get listed Verify Private registry Pricing

A private registry for your own capabilities

Your agents need to know which internal services exist, which are approved, and which they are allowed to call. That is a registry problem, and right now most organisations solve it by pasting a list into a system prompt.

One query, both worlds

An agent asks one question and gets your internal services and the public index ranked together, each labelled. No second endpoint, no deciding in advance which index to search.

curl -s https://wellknownhq.com/registry/search \
  -H 'authorization: Bearer wk_...' \
  -H 'content-type: application/json' \
  -d '{"query":{"text":"look up an employee record"}}'

  97  ACME Staff Directory      private   org-wide
  89  ACME Payroll Service      private   finance
  53  redis-mcp                 public
  31  agent-observability       public

The same question from an agent holding support instead of finance never sees the payroll service. Not redacted, not "1 result hidden". Absent.

Which agent sees which capability

Scopes

Label a capability finance and only agents holding that scope find it. A capability with no label is visible to every agent in your organisation, which is the safe default for a resource: adding a label narrows access, it never widens it.

Keys

Each key carries its own scopes, so your finance agents and your support agents use different credentials. A key with no scopes sees org-wide capabilities and nothing else. Least privilege on the credential, safe default on the resource.

Isolation

Your capabilities live under their own storage partition, not behind a filter in our application code. A query that does not carry your key cannot reach them even if every filter above it is wrong.

Publishing is a toggle

Anything private can be made public with one click, and back again. A capability is never in both places at once wondering which copy is true. Nothing is published unless you publish it.

Pricing

Free

Enough to put your real internal services in front of a real agent.

10 private capabilities
2 API keys, each with its own scopes
Scoped access: decide which agents see which capabilities
Merged queries: your internal services and the public index in one answer
Access log: which key saw what, and when

Create a registry

Team

$99 / month

For an organisation running agents against its own systems.

500 private capabilities
20 API keys
Everything in Free
Publish any capability to the public registry with one toggle

Upgrade in the console

Start with your real services

No sales call, no demo. Paste a catalog, mint a key, point an agent at it.

Create a registry