Amazon SP-API
Catalog, orders, fulfillment, brand analytics. Read-continuous. Writes (listings, inventory) pass the operator gate.
PLATFORM / INTEGRATIONS
The platform connects where operating decisions happen.
Integrations are first-class in the platform. Every connector inherits the substrate contract: explainable, idempotent, reversible. Credentials live encrypted under operator control; nothing leaves the operating perimeter without an audit trail.
MARKETPLACE & ADS
Marketplace surfaces where the platform reads and writes.
The platform integrates with the marketplace APIs that drive operating decisions. Reads are continuous; writes pass the side-effect gate.
Amazon Ads API
Campaigns, bids, search terms, audit log. The Amazon Ads capability is built on top.
Google Search Console
10+ properties via mcp-gsc. The Search Intelligence capability consumes this.
COMMERCE & CONTENT
Commerce and content surfaces the platform operates with.
Beyond marketplaces, the platform connects to commerce platforms, CMSs and forms — the surfaces where customer-facing surfaces and brand state live.
Shopify
Catalog, orders, draft orders. Multi-tenant ready, used across active commerce surfaces.
WordPress REST
Read + write content. Used for migration loops and parity audits.
Tally Forms
Form ingestion + autoresponder trigger. Active on 3plspain.
INTEGRATION CONTRACT
Every integration inherits the substrate.
An integration is not a script — it is a connector that follows the platform contract. Reads are logged. Writes are gated. Credentials are encrypted. Audit is mandatory.
web-builder / production route
Canonical route /platform/integrations/
Surface state integration contract
Credential encryption Secrets live in pgcrypto with APP_MASTER_KEY. Never logged. Never committed.
invariant
Read instrumentation Every API read is wrapped in worker_run context. Latency, errors and rate-limit signals are observed.
invariant
Write gate Writes that mutate external state (Amazon, Shopify, DNS, real emails) require operator approval in chat. Always.
invariant
Failure containment An integration failure stops the dependent capability — it never silently emits stale or guessed data.
invariant
New integration gate operator approval
A new integration is added only when the use case is concrete. No speculative connectors.
MISSING SOMETHING
If your operation depends on a surface not listed here, the conversation starts with the use case, not the connector.
The platform is opinionated about which integrations get built — only when the operating job is clear. If you have a surface that matters and a job worth doing, talk to us.
Talk about your stack