Vendor Listing
Onboard a vendor who wants their API listed in the treg catalog.
Install
npx skills add superdesigndev/treg --skill vendor-listing -g -a claude-code -y- Repository
- superdesigndev/treg7k
- Category
- Testing
- Updated
- 3d ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Onboard a vendor who wants their API listed in the treg catalog. Use whenever someone asks "how do we get listed on treg", a vendor sends their API details, or a listing PR/issue needs review. Walks the whole pipeline: eligibility gate → registry entry → platform-key slot → logo → tests → LIVE bogus-key test → core catalog YAML → verify → scrub → validate → evidence ledger in the PR. Every listing ships tier-4 wiring and a per-endpoint verification table. The vendor-facing doc this skill implements is docs/VENDORS.md.
Vendor listing, add a provider to the catalog
A listing has three parts, and all three ship in the same PR:
- Registry entry (
src/treg/oauth_providers.py), how a team connects a credential for the provider, and how treg verifies that credential is real. - Core catalog file (
src/treg/catalog/<service>.yaml), what an agent can do: 8, 15 curated endpoints with capability mapping, inputs, cost + provenance, and verified examples. - Platform-key slot (
config.py+fx.yaml), so treg can serve the endpoints on its own key (tier 4). Always aim for this. A listing that is BYOK-only is the exception and needs a stated reason (no self-serve pricing,own_accountdata, sales-gated).
And every listing PR carries a verification evidence ledger (Step 7b). No ledger, no merge.
Deep references (read before non-trivial work; do not duplicate them here):
docs/context/guides/expanding-a-category.md, the add-a-provider playbook, verify toolbox, trapsdocs/context/architecture/catalog.md, catalog schema, cost provenance, verify pipeline, PII rulesdocs/VENDORS.md, what we told the vendor to prepare (their checklist)src/treg/web/vendor-listing.md, the HOSTED instructions (served at/vendor-listing) that a vendor's own coding agent follows to raise a listing PR; the dashboard's "List as vendor" modal (connections view,vendorAskinindex.html) hands vendors a prompt pointing at it. Keep the three vendor-facing surfaces (doc, hosted page, modal prompt) telling one story.
Step 0, intake: collect the vendor facts
Before touching code, you need ALL of these. If the vendor's submission is missing any, ask, do not guess ("unconfirmed" beats a wrong path shipped):
