From zero to a published widget.

Create your account

Sign in to Widport and open the workspace. Your Clerk identity protects every control-plane operation.

What to enter

Sign in and confirm the dashboard opens on widport.com itself.

Create organization, project, environment, and namespace

This hierarchy defines ownership and isolation. Create it in this order: Organization (company/team) → Project (site/product) → Environment (production, staging, or development) → Namespace (the widget knowledge boundary).

What to enter

Use stable names. Example: Acme → Website → production → support. Wait for ready; if partial_failure appears, reconcile the organization before continuing.

Connect Model BYOK

Widport provisions the same authorized credential server-to-server in IntentParse and GQueries. The key is never returned to the browser.

What to enter

Choose the environment, keep DeepSeek as default or select another provider, paste the API key, and test it. Status should become active/ready.

Create a deployment and authorize domains

The deployment creates the public widget key and limits which sites may call the API.

What to enter

Choose the namespace, name it, and enter full origins with https:// and no paths. Separate origins with commas, semicolons, or new lines: https://example.com, https://www.example.com.

Enable automatic routing

IntentParse first selects the domain and then runs the specialized schema. The client does not need to choose one.

What to enter

Open Schemas and keep Automatic (recommended). Pin a schema only as an advanced override for a dedicated deployment.

Add knowledge

Register content the widget is authorized to use: documentation, FAQs, policies, and reviewed instructions.

What to enter

Under Knowledge sources, select a namespace and enter a name, HTTPS provenance URL, language, classification, and approved content.

Scan, review, and publish

Saving a source does not automatically make it evidence. A scan normalizes it and creates a candidate; human review controls what reaches GQueries.

What to enter

Run the scan, open Review queue, then approve and publish. Confirm it under Published memories. Revoking removes evidence from the index.

Configure the experience

Set appearance, capabilities, schema, policies, and human handoff. In auto mode, the widget inherits the host site's light/dark theme and accent.

What to enter

Review every tab. Keep require evidence enabled for factual answers; configure fallback/handoff and enable only actions your backend supports.

Install the widget

Place the tag before </body> on every page where Widport should appear.

What to enter

Replace wp_pub_your_deployment_key with the public key shown in Deployments. Adjust data-locale and data-position; never put a BYOK secret in HTML.

<script
  src="https://cdn.widport.com/v1/widget.js?v=1.1.3"
  data-project="wp_pub_your_deployment_key"
  data-locale="pt-BR"
  data-position="bottom-right">
</script>

Test end to end

Open your site on an authorized origin and ask both covered and uncovered questions.

What to enter

Covered answers should cite evidence. Missing evidence should trigger clarification or human handoff. Monitor Journeys and Usage.