superdesigndev/treg

OpenRouter for agent tools. Join community here: https://discord.gg/6mQYYfFMAn

View on GitHub ↗Jump to charts ↓Open shareable report →

superdesigndev/treg has 5.5k+ stars and 450+ forks on GitHub, is written in Python, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on September 24th, 2026
Created on July 15th, 2026
Open Issues & Pull Requests: 166 (+0)
GitHub issues: Enabled
Number of forks: 483
Total Stargazers: 5,751 (+0)
Total Subscribers: 16 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.9 hours
Mean response time: 44.8 hours
90th percentile: 46.3 hours
Tracked items: 10

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 19
New in 7 days: 6
Closed in 7 days: 0
Avg open age: 7 days
Stale 30+ days: 6
Stale 90+ days: 0

Recent activity

Opened in 7 days: 6
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • needs-triage (4)
  • bug (3)
  • enhancement (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Treg is a registry and proxy service that provides unified access to thousands of third-party APIs and internal tools through a single token and base URL.

The tool solves the problem of managing scattered API credentials, expensive vendor subscriptions, and fragmented tool access across agent teams. It works by maintaining a catalog of over three thousand endpoints from more than sixty providers—covering data enrichment, content generation, scraping, and other services—and proxying requests through its own infrastructure. For internal tools, it stores credentials server-side and injects them into requests, so callers never handle keys directly. The proxy relays requests without modeling or transforming upstream responses, preserving compatibility as APIs change.

Teams should adopt Treg if they run agents that need access to multiple paid APIs without individual subscriptions, want to share internal tools and credentials across teammates without exposing secrets, or prefer per-call pricing over monthly vendor fees. The catalog includes endpoints priced from fractions of a cent per call, with no provider signup required. Users can also register their own API keys, OAuth connections, vendor CLIs, or custom skills alongside catalog tools, all callable through the same interface. The tool suits organizations building agent workflows that span both external data sources and internal systems.

The project shows active development with regular updates to the catalog and tooling. The maintainers respond to issues and pull requests, indicating ongoing engagement with users. The codebase receives commits addressing bug fixes, feature additions, and documentation improvements. Community discussion happens through the linked Discord server, suggesting the team maintains direct contact with adopters.