Agents that do real work need many external APIs and credentials — SEO, enrichment, social publishing, image/video/voice generation, scraping and more — and most of those services sit behind subscriptions or per-vendor signup walls. This creates friction for automated agents and teams: distributing keys is insecure, per-vendor seats are expensive, and wiring each provider into an agent is brittle.
What Sets It Apart
- Single-token catalog and proxy: one X-Treg-Token gives an agent controlled access to a curated catalog of thousands of endpoints across many providers, so you ask for the job ("find backlinks", "get a user profile") instead of remembering vendor names.
- Pay-per-call + optional team-owned keys: anonymous or treg-served calls are priced up front (from a cent) and billed to a team balance; teams can also register their own provider keys or CLIs and those calls route unmetered through the registry.
- Server-side credential injection and audit: secrets (API keys, OAuth tokens, CLI creds) are injected server-side and never exposed to callers, while every proxied call is auditable — reduces key sprawl and leak risk.
- Skills and CLIs as first-class citizens: register SKILL.md recipes, vendor CLIs and multi-tool bundles so agents run end-to-end workflows without local secrets or per-agent configuration.
Who It's For & Trade-offs
Great fit if you run autonomous agents or multi-agent workflows that need broad, repeatable access to external APIs without copying provider credentials into every agent. It speeds prototyping (no per-vendor signup) and centralizes billing and credential health for teams.
Look elsewhere if you need a minimal single‑purpose SDK or direct, unproxied low-latency access to a single vendor (treg adds a relay hop and governance layer). Self-hosting requires typical infra (Postgres/Redis, Fernet key backups) and an operator willingness to manage a central registry and its billing model.
Where It Fits
Think of treg as “OpenRouter for tools” rather than models: where OpenRouter standardizes model access, treg standardizes tool access (APIs, CLIs, OAuth integrations, skill recipes). Use it as agent infrastructure that delegates provider choice, enforces org boundaries, and simplifies multi-provider experimentation.
How It Works (brief)
Calls resolve a tool (catalog entry or team-owned tool) → decrypt stored secret(s) → inject auth server-side via header/query/CLI env → stream to upstream as a faithful relay. Credential ladder: team tool key → registered secret → verified public route → treg-owned key. The CLI mirrors the API and exposes commands for search, call, balance, upload and skill management without exposing provider secrets.
