treg.

Tool registry for agents

The key never
leaves the server.

Point an agent at one base URL with one token. Credentials are injected on the way through, so the caller never holds them.

The one rule, quoted

The proxy relays, never models, the upstream, and injects auth server-side, so it survives upstream API changes and callers never hold keys.

request path
Agent holds no key
Your agent
one token
no provider key
treg
relay
holds the credential
Upstream
provider API
sees an authorised request

Illustrative path. The credential sits in the middle box and stays there.

catalog
Served with treg's key or a verified public route, billed per call.
your own
Your key always wins over treg's, and those calls are never metered.

Both rows restate the project's own description of the two tool kinds.
Pricing and provider counts are on the project site; they are not reproduced here.

Ask for the task

Search the catalog by what you want to do, rather than knowing which vendor sells the data.

Share a team credential

A registered account, OAuth connection, vendor CLI or skill, callable without handing the secret around.

Self-host it

The hosted registry runs at treg.to, and the project states anyone can self-host.