Answer
Four outside partners feed Brew, treg and Apify for data and Sloosh and Higgsfield for making, each on one account we own, each capped, and none spending without a rule or a person's yes; this page holds the accounts, the state of each, the limits and what is still missing, while the rules for using them live in Outside data rules and Image and video makers.
Today
The four partners
| Partner | What for | Account and key | State on 26 Oct | Source |
|---|---|---|---|---|
| treg.to | Data only: listening, SERP, keywords, reviews, AI answers, rival ads, shopping | Agent key brew-live, team squareup, TREG_TOKEN version 2; version 1 disabled |
Live on both sites | brew/treg.js:1-5 memory brew-apify-watch |
| Apify | Indian marketplaces, quick commerce, Similarweb, Instagram mentions, Trustpilot backup | Starter plan bought 23 Oct, account originative_crupper, APIFY_TOKEN |
Live | brew/apify.js:1-4 memory brew-apify-watch |
| Sloosh, sloosh.ai | Finals: go-live images and videos behind Make the final, over MCP only | Brew's own workspace, OAuth 2.1 at clerk.app.shopos.ai; Pro plan, 530 credits on 18 Oct | Connected on staging; off on production by Param's call on 25 Oct, finals there use Gemini | memory brew-sloosh-finals brew/server.js:592-593 brew/tools/prod-env.sh:9 |
| Higgsfield | Studio pictures and films through its keyed REST API, 84 workflows | HF_API_KEY_ID and HF_API_KEY_SECRET; added at deploy only if the secret exists |
Funded with $100 on 23 Oct; keys not in Secret Manager on 23 Oct; paid safety code on origin/main since 26 Oct | brew/jam2/higgsfield.js:1-5, 49 brew/deploy.sh:37 memory brew-jam-v2 memory brew-higgsfield-wiring |
Drafts run on our own Vertex keys, Gemini image, Veo and Gemini TTS, never through treg memory treg-usage-rules.
Limits and caps
| Cap | Value | Source |
|---|---|---|
| treg spend a day | TREG_DAY_CAP_USD 40 on staging and production, 15 on the demo |
brew/tools/prod-env.sh:9 brew/deploy.sh:41 |
| treg calls a day | 20,000 on the brew-live key | memory brew-apify-watch |
| Apify spend per brand a month | APIFY_BRAND_MONTH_CAP_USD 10 |
brew/tools/prod-env.sh:9 brew/SCOPE.md:15 |
| Sloosh credits a day, all brands | DAILY_CREDITS_CAP, default 300 |
brew/budget.js:13 |
| Sloosh agent limit | 50 credits a day on the workspace | memory brew-sloosh-finals |
| Higgsfield | No dollar cap in code; every request is priced first and the caller asks a person | brew/jam2/higgsfield.js:1-5 |
What each partner cannot do
- treg has no Indian marketplaces, request 1171, no holiday calendar and no video understanding memory treg-catalog-for-brew.
- Sloosh has no Veo; its quotes refuse sound settings on some video models memory brew-sloosh-finals.
- Higgsfield's REST API lacks Marketing Studio video modes, the photoshoot and marketplace prompt enhancers, brand kits, audio, upscale, background removal, Nano Banana, Veo, Seedream and GPT Image; those are CLI only on a personal login, and its terms make one CLI login for many brands risky memory brew-higgsfield-wiring.
Who we talk to
No source names a contact person at treg, Apify, Sloosh or Higgsfield. Account emails on file: treg on this Mac is signed in on Param's account for team squareup, and hello@ holds a second team, squareup-2, with $1 memory brew-apify-watch. Sloosh's staging workspace was connected by hello@joinsquareup.com memory brew-sloosh-finals.
How we find out something broke
The app's daily alerts cover the treg balance and Sloosh; Sloosh alerts are off on production with SLOOSH_CHECK=0 brew/docs/production.md:115 brew/server.js:592-593. Source health for every treg and Apify call is at /api/admin/sources memory brew-apify-watch.
Tomorrow
| Item | Version | Tag |
|---|---|---|
| treg first, Apify only for gaps | v1 | Stays |
| Higgsfield keys in Secret Manager so Studio makes go live | v1 | Changes |
Sloosh on production, after a staff sign in at /api/ops/sloosh/connect |
v1 | Changes, Param's call |
| Higgsfield Enterprise for the CLI only features | v2 | New, only after talking to Higgsfield sales |
| fal, HeyGen and ElevenLabs connected for the jobs the router already names | v2 | New |
| A named contact and a monthly invoice for each partner | v1 | New |
Rows that change or add are proposals for Param, not decisions.
How we do it
- Before saying treg is empty, check the live balance; never trust old logs memory treg-usage-rules.
- Never generate an asset through treg memory treg-usage-rules.
- No paid probe while building: test with
AI_MOCK=1, and ask Param before any paid call memory no-spend-while-building memory brew-higgsfield-wiring. - Read
data/sloosh-tools.jsonbefore touching a Sloosh call; re-run the probe when Sloosh changes a schema:
node tools/sloosh-probe.mjs
memory brew-sloosh-finals
- Refresh the Higgsfield catalog only with the guard that refuses an empty or shrunken one:
node tools/hf-catalog.mjs
memory brew-higgsfield-wiring
- Never call the Higgsfield CLI from the server memory brew-higgsfield-wiring.
- Never spend Sloosh credits without Param's yes on the quote memory brew-sloosh-finals.
Numbers
| Metric | Definition | Where measured |
|---|---|---|
| treg spend | Dollars a day and a month, by tag | spend/<month>.json per brand; treg balance |
| Apify spend per brand | Dollars a month against the $10 cap | spend/<month>.json, tags apify… brew/SCOPE.md:15 |
| Source health | Share of calls ok, empty or error per source | /api/admin/sources memory brew-apify-watch |
| Sloosh credits used | Credits charged per final | /api/ops/sloosh |
| Higgsfield spend | Dollars per make and per brand | Proposed, from bd.hfJobs |
Open
- Who is our contact at each partner? Proposal: Param names one person per partner and the email they answer, and this page lists them.
- Put the Higgsfield keys in Secret Manager now? Proposal: yes, on staging only, with the AI_MOCK tests passing first; production after one paid Studio make on a test brand with Param's yes.
- Sloosh on production. Proposal: keep it off until a design partner asks for a Sloosh final; then sign in on production and turn
SLOOSH_CHECKon. - Talk to Higgsfield sales about Enterprise? Proposal: yes, one call, to ask whether many brands on one account is allowed for the CLI only features.
- Which treg account owns the bill? Treg runs on Param's own sign in for team squareup. Proposal: move the team's billing to a company email.