One org key · every client shop

For agencies & feed operators

One agent. Every client’s feed.

Stop logging into ten dashboards to chase ten sets of disapprovals. Connect one AI agent to Simple Product Feeds with a single organization key, and audit, fix, and publish product feeds across your entire client portfolio — preview-first, fully audited, on your terms.

Works with Claude, ChatGPT, Codex & Cursor · Every write is previewed and logged

The problem

Every client store is its own fire drill

Feed work doesn’t scale by adding logins. Each client is a separate dashboard, a separate disapproval queue, a separate context you have to reload in your head. The more clients you win, the more the same manual fixes eat your team’s week — and the easier it is for a broken feed to sit unnoticed on someone’s store.

N logins

One dashboard per client. Twenty clients, twenty places to look.

Same fixes, again

The playbook lives in your team’s heads and gets rebuilt by hand on every new store.

Silent breakage

A disapproval on client #14 doesn’t reach you until spend drops.

The mechanism

One connection, scoped to every client

You connect your agent once with an organization key. Every request names the client store it acts on, so a single agent operates safely across your whole portfolio — no re-authenticating, no store-hopping.

spf_org_sk_… one agent connection →
northwind-supply 3 disapprovals
harbor-goods clean
atlas-outfitters 12 missing GTINs
maison-lume clean
peak-and-pine margin tiers set
verde-market 1 feed stale

“Audit every client feed and show me who has disapprovals.” → one pass, whole portfolio.

Portfolio in one place

One key spans every client shop. Ask once and the agent sweeps the whole portfolio — health, disapprovals, stale feeds — instead of you opening them one by one.

Playbooks as reusable rules

Your method — how you fix titles, exclude junk, tier by margin — is expressed as rules. Codify it once, apply the same playbook to each new client instead of rebuilding by hand.

Client-safe by construction

Every write previews first and waits for your OK. Every change is logged with per-row lineage. Nothing touches a client feed that you didn’t see and approve.

How it works

From zero to portfolio-wide in three steps

01

Get an org key

Install on your client stores and generate one organization API key that spans them all.

02

Connect your agent

Point Claude, ChatGPT, Codex, or Cursor at the Simple Product Feeds server. One connection, done once.

03

Operate across shops

Audit, fix, and publish feeds for any client by name — preview each change, then ship it.

Straight talk

Live today: agent-driven cross-store operations via the organization key — one agent, every client shop, real work getting done. On the roadmap: a standalone portfolio dashboard that rolls the same data up visually. We ship the operating layer first and tell you plainly what’s a screen versus what’s real.

Free portfolio feed audit

See what an agent would find across your clients

Tell us where to look and we’ll run the same sweep an agent runs — the disapprovals, the missing fields, the stale feeds — and send it back ranked, with the quick wins first. No pitch, just the findings.

  • Feed health across your client stores, in one report
  • The exact fixes an agent would preview for you
  • Which wins are one rule away

No spam. We'll only email you about your audit and how to run it yourself.

Frequently Asked Questions

Do I need a separate connection for every client store?
No. You connect once with a single organization API key and scope each operation to a client store — either by naming the client to your agent, or with a shop_id parameter on the API. One agent, one key, your whole portfolio.
Is this safe to run on client stores?
Yes — that is the whole design. Every write is preview-first: the agent shows you the exact before/after diff and waits for your confirmation before anything publishes. Every change is recorded in an audit trail, and per-row lineage shows precisely what changed and why. Nothing happens to a client feed that you did not see and approve.
Can I reuse my agency's playbook across clients?
Yes. The way you fix feeds is expressed as rules — exclude out-of-stock, normalize titles, set margin tiers by category. Those rules are reusable: codify your agency’s method once and apply the same playbook to each new client store instead of rebuilding it by hand every time.
What's live today, and what's on the roadmap?
Live today: agent-driven cross-store operations via the organization key — audit, fix, and publish across every client shop from one agent connection. On the roadmap: a standalone portfolio dashboard that rolls the same data up visually. We would rather ship the operating layer first and be honest about what is a screen versus what is real.
What does it cost?
One flat rate for your whole book: the Agency plan is $99/month for all your connected client stores — up to 50,000 SKUs across the portfolio — instead of paying per store, which multiplies with every client you win. Every store still starts free while you evaluate; you move to the Agency plan when you connect a portfolio. We onboard early agencies personally, so reach out and we set it up with you.
Free to start · $99/mo flat for your whole portfolio

Run your whole book from one agent

One connection, every client feed, every change previewed and logged. Bring the agent your team already uses.