Every Specicon deployment follows the same path. Nothing below requires replacing your commerce platform, CMS or CRM.
Connect the catalogue, review readiness, generate a key, test in the sandbox, publish — then watch the outcomes land.
Organisation, region and the people who need access.
This sets the decision language: which Option DNA applies and which requirements matter.
Platform credentials, REST API, CSV or a direct database connection.
Products, services, properties, courses or policies — whatever is being decided about.
What can already be recommended, what is missing key facts, what needs a human look.
Which declared, behavioural and contextual signals you are able and permitted to send.
Margin, retention, inventory position, service load — the objective the ranking serves.
Separate sandbox and live keys, scoped per surface.
A real request and response with no production impact.
Embedded, headless, assistant, search or support console.
Send back what happened: viewed, compared, accepted, purchased, returned, rated.
Go live on one surface, with an agreed measurement period and a holdout group.
Screens are representative of the demo environment. No real credentials or customer data appear.
Specicon’s value is in how the decision is reached. These configuration surfaces exist in the product and are covered under agreement — they are not published.
The complete API inventory, full request schemas and administrative routes live in authenticated developer documentation. API overview.
