2,800+ tools for agents
Connect an account once. treg holds the credential server-side and injects it on every call — nothing lands on your machine.
{{g.category}}{{g.total}}
{{g.hint}}| {{p.display_name}}{{p.summary}} | {{p.auth_kind==='key'?'API key':(p.auth_kind==='token'?'your own bot':'one-click')}} | {{connCount[p.service]}} connected not configured not connected |
{{mkProvider.display_name}}
{{mkProvider.category}} · {{mkProvider.base_url}}
{{mkProvider.summary}}
| {{c.identity_label || c.name}} {{c.resource_name || c.resource_ref || (c.supports_discovery ? 'no '+(c.resource_label||'account')+' chosen yet' : 'whole account')}} | {{c.name}} | working setup required failing expired expiring manual renew needs a second credential {{cap}} |
{{mkCapabilityIntro(cap)}}
- ✓{{d.label}}
{{platLabel}}
Every endpoint treg knows for this platform, one ledger, filed by subject — jobs several providers do sit on a single row, so you can compare price and coverage before you spend a call.
| What it does | Providers / route | Price | ✓ | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| {{sec.domain}} {{sec.rows.length}} | |||||||||||
|
▸
{{r.title}}
|
{{pill.name}}{{pill.price}}✓
+{{r.pillsMore}}
{{r.endpoints[0].provider_display||r.endpoints[0].provider}}
{{endpointAccessLabel(r.endpoints[0])}}{{r.endpoints[0].method}}{{r.endpoints[0].path}}{{r.endpoints[0].kind}}
|
{{r.price}}({{r.priceNative}}) | ✓· | ||||||||
|
{{e.provider_display||e.provider}}
{{e.method}}{{e.path}}
{{endpointAccessLabel(e)}}
{{costShort(e.cost)}}({{costNative(e.cost)}})
verified {{e.verified}}
unverified
your account
any account
{{e.tier}}
{{e.summary||'No summary in the catalog for this endpoint.'}} Parameters
{{e.input.note}} {{s.label}}{{s.type}}
The catalog has no parameter reference for this endpoint yet — the provider's docs have them.
{{e.call_template}}
{{e.id}}
Loading the captured response…
{{platEx[e.id].err}}
{{platEx[e.id].text}}
|
|||||||||||
Bring your own keys & skills
Call any of these with no key on your machine. Copy a snippet, or Try it here.
Register an upstream API here, then call it with no key on your machine.
| {{t.name}} | {{t.host}} | ⌘ run{{t.cli.enabled?'':' off'}}serverlocal-only{{w.label}} |
| {{r.name}} | treg skill install {{r.name}} | ||
Nothing here{{q?' matches "'+q+'"':' yet'}}. This is your personal space - your team's tools live under another org. Switch to a team →
Nothing of your own yet — but you can already call 2,800+ tools
New verified accounts get $1.00 of free credit once when creating an eligible team, so the catalog works before you register anything: find a tool by what it does, see the price, call it. Browse the catalog →
When you're ready to add your own keys and skills — your .env and skill folders — load them here and they become callable tools for the whole team.
curl -fsSL {{proxy}}/install.sh | sh treg login
# preview what's here (read-only) treg scan # register keys + skills treg upload --all
One line, token included — your agent reads llms.txt, installs the CLI, signs in, and registers your skills + keys (read-only scan first, you approve).
{{buildAgentPrompt('agent', true)}}{{detail.name}} {{detail.kind==='skill' ? 'skill' : (detailData&&detailData.cli ? 'endpoint + CLI' : 'endpoint')}} {{detailData.owner}}
Loading…
Use with your agent
Send someone this page's link, or paste this into a coding agent (Claude Code / Codex / Gemini) — it installs the CLI, signs them in as themselves, and pulls just this skill. Its credential{{detailData.secrets.length>1?'s stay':' stays'}} server-side — calls go through the proxy, no key lands on their machine.
{{detailPrompt}}
Use with your agent
Send someone this page's link, or paste this into a coding agent. Calls go through the proxy — the credential is injected server-side, never on their machine.
{{detailPrompt}}
{{detailData.base_url}}
{{w.label}} injected server-side on every call — the value never appears here or on a caller's machine.
none — a public upstream, no credential needed.
treg run {{detail.name}} -- <args> server local-only ⌘ run off
runs matching these patterns are refused before the key is injected: {{p}}
▚ {{detailParentSkill.name}} — the recipe + files that registered this tool.
Bring your own keys & skills
The credentials your tools inject. Values are encrypted server-side and never shown.
| {{s.name}} | {{s.kind}} | owner: {{short(s.owner)}} |
No secrets yet — add one below, or bulk-load everything at once (setup guide under the form).
Name a key after its catalog provider — e.g. {{keyNameSuggestions.slice(0,3).map(p=>p.service).join(', ')}} — and catalog calls use it automatically. The name field suggests every provider that takes a pasted key.
Tip: paste a whole .env into the name field — it splits into rows automatically.
A param is non-secret config (project id, org id) — injected alongside a credential into CLI env or an HTTP query.
Add your own keys & skills
Bulk-load your keys (and skills) from your machine — each lands here encrypted, referenced by name.
curl -fsSL {{proxy}}/install.sh | sh treg login
# preview what's here (read-only) treg scan # register keys + skills treg upload --all
One line, token included — your agent reads llms.txt, installs the CLI, signs in, and registers your skills + keys (read-only scan first, you approve).
{{buildAgentPrompt('agent', true)}}Team: {{activeName}}personal
You are {{activeRole}} here. Switch, create or join a team from the picker at the top of the sidebar.
Members, projects and policy are visible to admins.
Your usage today: {{myUsage.used_today}} / {{myUsage.cap}} calls.
The previous key stopped working immediately. Update {{newAgent.name}} everywhere it runs before closing this card.
This is the only time it is shown. Put it in the agent's TREG_TOKEN. Anyone holding it can act as {{newAgent.name}}, so keep it in an environment variable or secret manager — never commit or share it.
✓ connected — {{newAgent.name}} called in as itself
waiting for its first check-in…
Snippets carry the real token (minted this page-load — the server only keeps a hash).
The server stores only a hash of the token, so it can't be shown again — these snippets use $TREG_TOKEN. (the old token stops working)
{{agentSnippet}}
Put this wherever the agent runs — a .env, a CI secret, or its config.
Daily cap = how many calls + runs a member may make per day. -1 = unlimited.
Tools = which endpoints/CLIs a member may call or run. Local run = may run CLIs on their own machine (off = server only). The owner always has full access.
| Role | Today | Daily cap | Tools | Local run | ||
|---|---|---|---|---|---|---|
| ↳ {{m.client}} detected
runs as {{short(m.member)}} — inherits their full access |
— | {{m.used_today}} | {{m.calls_30d}} calls in 30 days · last seen {{when(m.last_seen)}} | |||
|
↳ {{m.name}} agent
{{m.created_by?('owned by '+short(m.created_by)):'machine identity'}}
Its current key will stop immediately. The next card shows the replacement once so you can update {{m.name}}.
This removes the agent and revokes all its keys. Activity stays for audit; restoring it means creating and configuring it again.
{{m.email}}
|
{{m.role}} | {{m.used_today}} | All | |||
|
Tools & skills {{m.email}} may use/see — uncheck to withhold. All checked = full access (and new ones apply automatically).
No tools registered yet.
Projects {{m.email}} may use — all checked = every project (and new ones apply automatically). Tools with no project stay visible to everyone.
Tip: create a project to scope members to just part of the team's tools. |
||||||
A member is a person who signs in. An agent is a machine identity with its own token — capped, scoped and logged as itself. Scope either with Tools and Projects above.
{{promoteHint}}
Cap -1 = unlimited. An agent can never be an owner, and can never sign in — its token is the only way to act as it.
{{lastInvite.code}}| Role | Invited by | Expires | ||
|---|---|---|---|---|
| {{inv.email}} | {{inv.role}} | {{short(inv.invited_by)}} | {{inv.expires_at?until(inv.expires_at):'never'}} |
No pending invites.
Use more than one key without making a new team member. Permissions, limits, and billing stay with the assigned identity.
The previous key stopped working immediately. Update every CLI, MCP installation, or other client using this team's Default key.
The previous key stopped working immediately and is now hidden from this list. Update {{newApiKey.assigned_name}} everywhere it runs before closing this card.
This team-specific key remains revealable on Getting Started.This is the only time treg shows the full key. The server stores only its hash. Anyone holding it can act as {{newApiKey.assigned_name}}, so keep it in an environment variable or secret manager — never commit or share it.
CLI users can run treg login again to save the new key. Update MCP and other clients manually.
{{agentSnippet}}Replace TREG_TOKEN in every environment, CI secret, secret manager, or agent config where {{newApiKey.assigned_name}} runs.
| Key | Status | Created | Last used | |
|---|---|---|---|---|
{{group.type==='human' && k.assigned_type==='agent'?k.assigned_name:k.name}}{{keyKind(k.kind)}}
|
{{k.state}} | {{k.created_at?when(k.created_at):'Unknown'}} | {{k.last_used_at?when(k.last_used_at):'Never'}} |
No keys are available.
Top-ups aren't configured on this deployment.
Auto top-up is set up and will switch on as soon as a top-up saves your card.
On - we add {{money(billing.autotopup.amount_micro)}} whenever the balance drops below {{money(billing.autotopup.threshold_micro)}}. This month: {{money(billing.autotopup.month_spend_micro)}}. {{autoOpen?'Cancel':'Edit'}} Keep agents running without watching the balance. We charge your saved card only when it dips below your threshold.
Loading…
No top-ups yet. Once you add funds, every payment shows up here with its invoice.
| {{bhistDate(i.created_at)}} | {{money(i.amount_micro)}} | {{i.auto?'auto':''}}+{{money(i.bonus_micro)}} bonus | {{bhistLabel(i)}} — |
Invoice links are temporarily unavailable — the amounts above are correct. Try again shortly, or use Manage billing for the full archive.
Loading…
A project groups tools inside this team, so a member or agent can be scoped to just part of it. A tool with no project stays visible to everyone. Secrets stay team-level — one shared credential can back tools in several projects; scope who uses them via member access.
No projects yet — every tool is team-wide.
| Project | Slug | Tools | |
|---|---|---|---|
| {{p.name}} | {{p.slug}} | ||
|
Tools in {{p.name}} — check to add, uncheck to make team-wide again. Checking a tool that lives in another project moves it here.
No tools registered yet.
|
|||
Block calls to a host, a path, or a method. Leave a field empty to mean any. Applies to the proxy and to runs — and to everyone, including owners.
No rules — nothing is blocked.
| Method | Host | Path | Applies to | Project | Note | |
|---|---|---|---|---|---|---|
| {{r.method||'any'}} | {{r.host||'any'}} | {{r.path_prefix||'any'}} | {{r.scope==='org'?'whole team':(denyWho(r.user_id))}} | {{r.project_id?projName(r.project_id):'any'}} | {{r.note}} |
treg blocks at three layers: the rules above (HTTP host/path/method, this team's policy), these per-tool argument patterns (from the skill's treg.json or the treg catalog — edit them there), and the OS sandbox around isolated local runs.
| Tool | Blocked argument patterns |
|---|---|
| {{t.tool}}off | {{pat.pattern}}· {{pat.source}} |
The most this team can spend per day on treg's keys. Resets at 00:00 UTC. None by default. Worth setting if agents run unattended with auto top-up on, since a balance that refills itself can't stop a runaway one.
Any amount, up or down. Leave it empty (or 0) for no daily limit — your balance is then the only bound.
Cap or block one of your own customers by the tags your calls carry
(X-Treg-Meta). Limits stack — a workspace ceiling and a
per-customer ceiling both apply, and a refusal names which one hit. They are
advisory: concurrent calls can overshoot slightly, and your balance is the
hard limit.
| {{dim}} | Daily limit | Status | |
|---|---|---|---|
| every {{dim}} (default) | {{defaultFor(dim)?fmtCap(defaultFor(dim)):'no limit'}} | — | |
| {{b.val}} | {{fmtCap(b)}} | {{b.status}} | |
| no exceptions — every {{dim}} follows the default | |||
The slug is the team's id in X-Treg-Org, treg org use and MCP. Changing it
keeps existing keys working; run treg org use {{renameSlug.trim()||activeSlugNow}} to re-pin the CLI.
{{renameErr}}
A personal team cannot be left or deleted. Create or join other teams from the picker at the top of the sidebar.
Activity - {{activeName}}
{{actOkOnly?'Successful calls and runs in this org.':'Every proxy call and server CLI run in this org.'}}
{{activityCachedCount}} of {{activityCallCount}} loaded {{activityCallCount===1?'call was':'calls were'}} served from the archive.
| When | Who | Key | Tagged | Tool | Action | Status | Cost |
|---|---|---|---|---|---|---|---|
| {{when(a.created_at)}} | {{activityWho(a)}}owner: {{activityOwner(a)}}via {{a.client}} | {{a.api_key_name}} · {{a.api_key_prefix}}— | {{k}}={{v}}— | {{a.tool}} | {{a.where||'run'}}{{a.action}}result ↗result via CLI{{a.task.ttl_note?'expires in '+a.task.ttl_note:'time-limited link'}} | {{a.status}}{{taskStateLabel(a.task)}}result › | hold {{a.cost!=null?money(a.cost):'—'}}Cached |
No activity yet.
No successful calls yet — show all {{activityRows.length}}.
Calls & runs per member over the last {{usageDays}} days. Counts only - no request or response content is stored.
| Member | API | Local | Server | Total |
|---|---|---|---|---|
| {{short(u.user_email)}} | {{u.call}} | {{u.local_run}} | {{u.server_run}} | {{u.total}} |
No usage in this window.
| Tool | Events |
|---|---|
| {{t.name}} | {{t.total}} |
| Day | Events |
|---|---|
| {{d.day}} | {{d.total}} |
What each {{key}} spent, from the ledger. A call is credited in full to every tag it carries, so these sections are different slices of the same money — never add two of them together.
| {{key}} | Calls | Spend |
|---|---|---|
| {{r.value}} | {{r.calls}} | {{money(r.charged_micro)}} |
| untagged | — | {{money(tagUsage[key].unattributed_micro)}} |
Nothing tagged {{key}} in this window.
Loading…
Platform admin
Cross-tenant control (super-admin). Suspend locks members out; delete cascades.
| Org | Members | Tools | Status | |
|---|---|---|---|---|
| {{o.name}} | {{o.members}} | {{o.tools}} | {{o.suspended?'suspended':'active'}} |
| Orgs | Flags | ||
|---|---|---|---|
| {{u.email}}you | {{u.orgs.length}} | super-admin suspended - | - you - |
Getting started
Setting up treg for {{welcomeAgent.name}}
First, install the treg plugin:
{{welcomeAgent.plugin ? "Then, in your Bot's chat, send:" : "In your agent's chat, send:"}}
{{welcomeSetupCmd}}Already created. Setup signs your agent in automatically — but if it ever asks for a key, give it this one (header X-Treg-Token).
{{startTokenShow ? myToken : (myToken.slice(0,14)+'••••••••••••••••')}}This team-specific Default key can be revealed here again. Additional and agent keys are random secrets shown only once because treg stores only their hashes.
This team's Default key is disabled, so it is hidden and cannot be used.
treg is ready with your agent. Copy any example below and send it to your agent.
Build on treg
Optional, for two other kinds of user. Each is a skill file — paste the line into your coding agent, in your own repo, and it implements the rest.
Put your API in front of every treg agent. Your agent reads the guide, writes the catalog entry for your endpoints and prices, and opens the PR.
Read {{proxy}}/vendor-listing.md and add our API to the
treg catalog, then open a PR.
Give your users 2,800+ tools without owning the keys — and bill each of your customers for what they used. Covers the call methods (HTTP, MCP, CLI), per-customer tagging, spend limits and invoicing.
Read {{proxy}}/integrate.md and integrate treg into our
product, including per-customer usage tracking and billing.
Prefer the terminal? Manual CLI setup & sharing your team's keys →
2,800+ catalogued endpoints: SEO and backlinks, social and trends, people and company enrichment, ads. Find one by what it does, see its price, call it — no provider signup. New verified accounts get $1.00 free credit once on an eligible team, covering hundreds of calls.
One line, token included — your agent reads llms.txt and does the rest: installs the CLI, signs in as you, and makes its first call.
{{buildAgentPrompt('agent', true)}}Installs the treg command and points it at this server. Upgrade later with treg update.
curl -fsSL {{proxy}}/install.sh | sh
Opens your browser — GitHub, Google, or an email code. Your first sign-in also registers you.
treg loginSearch the catalog by what you need done, check the price, call it, and see exactly what it cost.
treg catalog search "backlinks for a domain" treg call tikhub.tiktok.user.profile --query uniqueId=tiktok treg balance # see exactly what it cost
Share your skills & API keys with the team — your .env keys and skill folders become tools every teammate's agent can call, without the key ever leaving the server.
One line, token included — your agent reads llms.txt, installs the CLI, signs in as you, and can register your local skills + keys as shared tools (read-only scan first, you approve).
{{buildAgentPrompt('agent', true)}}Installs the treg command and points it at this server. Upgrade later with treg update.
curl -fsSL {{proxy}}/install.sh | sh
Opens your browser — GitHub, Google, or an email code. Your first sign-in also registers you.
treg loginTwo ways to give your agents power: share a whole skill, or register a single API endpoint. Preview with treg scan first. Idempotent — re-run freely.
treg upload # both .env + skills in this dir treg upload env --select openai,stripe treg upload skills --dir ~/.claude/skills --all # register skill from a specific path
Your team's own tools: a teammate pulls a shared skill and calls any registered API, with no keys on their machine. These are never metered — your team already pays for them.
Browse the shared library, pull a skill, and call a tool — the credential stays on the server, never on your machine.
treg skill ls treg skill install seo-blog-writer treg call https://api.stripe.com/v1/charges
{{refTab==='partner' ? 'Affiliate partner' : 'Refer a friend'}}
Revenue share, paid in cash. By invitation.
They get {{money(ref.terms.referred_micro)}} when they add {{money(ref.terms.min_topup_micro)}}. You get {{money(ref.terms.referrer_micro)}}, {{ref.terms.hold_days}} days later.
People who send real volume: an audience, a newsletter, a community, or a team that builds on treg for clients.
A share of what your referrals top up, paid to you in cash monthly. Not credit, and no {{ref.cap.limit}}-referral cap.
Invite only. Tell us about your audience and how you'd send people to treg, and we'll get back to you.
Apply to be an affiliate partnerJust want to tell a friend? The refer-a-friend program pays {{money(ref.terms.referrer_micro)}} in credit per friend, no application needed.
Loading…
Referral rewards are paid as credit into a team you own, so you'll need one first.
Your reward lands in {{ref.credit_org.name}}.
{{money(ref.totals.pending_micro)}} on the way — rewards land {{ref.terms.hold_days}} days after your friend adds funds.
That's as far as the self-serve program goes. If you're sending real volume, switch to the Affiliate partner tab above — we pay affiliate partners in cash.
Nobody yet. Share your link above.
| Who | Signed up | Status | Reward |
|---|---|---|---|
| {{r.email || '—'}} | {{bhistDate(r.signed_up_at)}} | {{refStatus(r)}} | {{money(r.reward_micro)}} — |
Tutorial
Four ways to learn treg - pick one.
▤ CLI tutorial
The whole registry from your terminal - copy each command and follow along. {{tutSteps.length}} steps.
▚ Dashboard tour
Everything you can do in this web UI, a screenshot per step. {{tourSteps.length}} steps.
▞ Import & shell
Turn the CLIs on your machine into team tools, then use them in a shell where they just work - plus the security sandbox. {{(tutData.importShell||[]).length}} steps.
▟ Team access control
Choose which tools each member may use, and whether they may run CLIs locally. {{(tutData.access||[]).length}} steps.
Tried the demo? Remove demo teammates →
CLI tutorial
| Action | {{c}} |
|---|---|
| {{r[0]}} | {{v?'✔':'✘'}} |