Choose a tier above and check out securely with Stripe. You'll receive your account API key by email (operator-provisioned while we're in pre-launch).

curl -X POST localhost:8094/api/v1/feeds \
  -H 'X-API-Key: fg_...' -H 'Content-Type: application/json' \
  -d '{"name":"Google Shopping","channel":"google",
       "webhook_url":"https://hooks.slack.com/..."}'
# -> {"feed_id": "feed_...", ...}

Keep your api_key safe — only its hash is stored server-side.

Export your feed from Shopify (or your feed tool) as CSV, then:

curl -X POST localhost:8094/api/v1/feeds/<feed_id>/audits \
  -H 'X-API-Key: fg_...' -H 'Content-Type: application/json' \
  -d '{"format":"csv","content":"<your feed csv>"}'
# -> {"score": 61, "band": "poor", "error_count": 4, ...}

TSV, XML, and JSON feeds work the same way — or POST a {"products": [...]} payload directly.

GET /api/v1/audits/<audit_id> returns every issue with the product, the rule, and the fix — or grab /export.csv for your spreadsheet. Fix in your store or feed tool, re-export, re-audit: the score delta shows your progress.

On Growth and Agency, hand the watching to FeedGuard: point it at your feed URL, pick a cadence, and it fetches and audits the feed itself.

curl -X PUT localhost:8094/api/v1/feeds/<feed_id>/schedule \
  -H 'X-API-Key: fg_...' -H 'Content-Type: application/json' \
  -d '{"source_url":"https://your-store.example.com/feed.csv",
       "interval_minutes":1440}'

Every scheduled run is recorded and diffed against the last — new error-severity issues POST to your webhook automatically, and a failed fetch shows up as a failed run, never as silence. Prefer your own pipeline? Calling the audit endpoint from your cron or CI works exactly as before.