The Hub

The Hub is the browser console for your account, at https://hub.<region>.luigisbox.ai — https://hub.eu1.luigisbox.ai for the EU region. Sign in with the same Luigi’s Box account you use everywhere else; there is nothing separate to provision.

Much of what this documentation shows as an API call can be done there instead. Where that is true, the page carries an In the Hub panel next to the call. It gives the click path as a trail — the section, the page, and the control you press — and says what the form does not cover.

What it covers

In the Hub	Does what	Written up under
Front-end Integration	Creates integration repositories, renames them, hands you the clone URL and the loader script URL	Repositories API
Channels	Creates, edits and deletes channels — name, catalog, visibility conditions, attribute projections	Account structure
Business Rules	Authors campaigns end to end: targeting, triggers, schedule, rules and effects, and the draft → active → paused → archived moves	Authoring API
Catalogs	Browses a catalog’s object types and objects, and shows each object’s stored attributes as raw JSON	Catalog metadata
Catalog History	Shows one object’s change timeline, each entry applied or still in flight	Object history

What it does not cover

These have no form in the Hub, and are done over the API:

• Sending catalog content — the Content API and feeds, including feed configuration and mappings.
• Creating organizations, catalogs, surfaces and tags — Account structure.
• Discovery requests — search, collections and recommendations.
• Reporting behaviour — sending events.
• Issuing and rotating credentials — Authentication.

Which one to reach for

The Hub and the API write the same records, so a channel created in one is the channel the other reads. Use whichever suits the job:

• The Hub for one-off setup and for anything a person decides — creating the integration repository, adding a market as a channel, running a merchandising campaign.
• The API for anything that has to repeat: provisioning per environment, campaigns generated from your own merchandising tooling, or configuration you keep in version control.

See also

• Account structure — the entities the Hub edits
• Your first integration — the fastest path to a storefront
• Authentication — the credentials behind both surfaces