CanonIQ API · Design Partner Beta

The permissioned context layer between people and products.

CanonIQ API lets approved products adapt around who a user is, what they need, and what they have consented to share.

Use CanonIQ to reduce cold starts, personalize onboarding, improve recommendations, route users to better next steps, and make context-aware experiences feel less generic — without exposing the full user profile.

Currently accepting early API conversations, design partner requests, and integration discovery.

Permissioned Profile Slice
slice_id · slc_8f24a
scoped
decision_stylevaluestiming_contextpreference_signalsconsent_scope
0.82
confidence
5
fields
v0.1
schema
Product Experience
→ personalized
  • Better recommendations
  • Smarter onboarding
  • More relevant offers
  • Clearer next action

Traditional sign-in tells your product who has access.

CanonIQ helps your product understand how to serve the person.

Permissioned profile slicesDeveloper-ready intelligence layerBuilt for personalization and conversion
Two sides of CanonIQ

One context layer. Two powerful uses.

CanonIQ becomes the context layer between the person and the internet — so users can bring their context with them, and products can adapt around it.

For users

Take your context with you.

Users should not have to explain themselves from scratch every time they open a new product. CanonIQ gives people a way to carry approved context across products, with control over what is used, where, and why.

  • Bring selected context into supported products
  • Reduce repetitive onboarding
  • Keep product-specific profiles separate from full CanonIQ
  • Control what can be used or suppressed
For companies

Adapt your product around the person.

Products can request approved CanonIQ profile slices and use them to personalize onboarding, recommendations, next actions, offers, resource routing, explanations, and interface defaults.

  • Improve cold-start personalization
  • Request only the context your surface needs
  • Personalize without receiving the full profile
  • Respect consent, sensitivity, and portability rules

Bring your CanonIQ with you.

The platform story

CanonIQ becomes the context layer between the person and the internet, allowing approved products to adapt around who the user is, what they need, and what they have consented to share.

Most products personalize from local behavior: what someone clicked, watched, bought, searched, or ignored. CanonIQ adds a traceable operating intelligence layer — what a person values, what they avoid, what they are trying to do, how they make decisions, and what kind of help is actually useful.

Why CanonIQ

Give your product the context it is missing.

Most AI products and recommendation systems start with limited context. They ask users to repeat themselves, generate generic outputs, or personalize from shallow demographic and behavioral signals. CanonIQ provides structured identity, values, decision, preference, context, timing, and intent signals that product teams can use to create more relevant experiences.

01

Reduce cold starts

Start with permissioned identity intelligence instead of making every product interaction begin from zero.

02

Personalize with purpose

Adapt recommendations, messaging, onboarding, offers, and product flows around how a person actually decides.

03

Improve conversion

Use better context to match the right message, moment, product, or next action to the user.

04

Reduce prompt waste

Give your preferred LLM structured context up front so it spends less effort reconstructing the user.

How it works

How CanonIQ works

01

User builds or connects context

A user creates CanonIQ or builds product-specific profile signals through supported experiences.

02

Product requests a profile slice

An approved product asks for only the context needed for a specific surface or use case.

03

CanonIQ applies consent and sensitivity rules

The API filters context based on user permission, product scope, sensitivity, and portability settings.

04

The product adapts the experience

The product can personalize onboarding, recommendations, resource routing, offers, copy, layout, defaults, or next actions.

What products can personalize

What products can adapt

Onboarding

Start closer to the user's actual needs instead of asking every question from scratch.

Recommendations

Rank options using approved context, moment signals, preferences, constraints, and feedback.

Ads and offers

Show more relevant offers at better moments without exposing the user's full profile.

Resource routing

Surface grants, jobs, providers, public benefits, programs, or tools based on location, need, eligibility, and consented context.

AI assistants

Make preferred LLMs or AI workflows work better with less repeated context.

Interface defaults

Adapt tone, layout, CTA priority, explanation depth, filters, and next actions.

Example

Better relevance at the right moment.

A media platform may know what a user watched, but still show irrelevant ads or offers. With CanonIQ, the product could request an approved surface-specific profile slice and learn that this user prefers practical, low-pressure offers, avoids fear-based messaging, and is most receptive to family-friendly or time-saving recommendations in the evening.

Instead of only asking "what did this user watch?", the product can ask "what kind of message, offer, or next action is actually useful for this person right now?"

Privacy note. The product does not need the full CanonIQ profile. It receives only the approved context required for that surface.
Streaming app · ad slot
Tone
Clear, practical, low-pressure
Relevance tags
family-friendlypracticaltime-saving
Avoid
fear_basedhigh_pressure
API capabilities

API capabilities

Signal ingestion

Products can send structured signals such as saves, dismissals, preferences, feedback, resource interests, and moment context.

Profile slices

Products can request approved profile context for a specific product or surface.

Surface personalization

CanonIQ can return personalization instructions such as default filters, tone, layout, CTA priority, relevance tags, and avoid tags.

User correction

Users can correct, suppress, or remove signals.

Consent and scope

CanonIQ enforces what can be used in-product, across Lumenfolk products, with partners, or not at all.

Sensitivity handling

Signals can be labeled public, low, private, sensitive, or restricted.

Sample response

Example: surface personalization response

canoniq.ai · v1
surface_personalization
{
  "surface": "ad_slot",
  "personalization": {
    "relevance_tags": ["family-friendly", "practical", "low-friction"],
    "avoid_tags": ["fear_based", "high_pressure"],
    "tone": "clear_practical",
    "timing_fit": "good",
    "explanation": "Use practical value-first offers and avoid high-pressure messaging."
  },
  "privacy": {
    "scope": "partner_surface_only",
    "sensitive_fields_removed": true,
    "full_profile_exposed": false
  }
}

CanonIQ should inform the experience without exposing the full person.

Permissioned by design

Profile slices, not profile dumps.

CanonIQ is designed to return only the context a product is allowed to use for a specific purpose. A recommendation surface, resource hub, onboarding flow, ad slot, or AI assistant may each receive different approved context.

  • Products do not receive the full CanonIQ by default.
  • Sensitive signals are filtered unless explicitly permitted and appropriate.
  • Users should be able to correct, suppress, or remove signals.
  • Product-specific profiles are not the same as full CanonIQ.
Features · Beta

CanonIQ API Features

Permissioned identity intelligence modules for products that need better personalization, recommendations, onboarding, and conversion.

CanonIQ API is currently in beta. Feature examples use sample data and may not represent final product behavior.

Beta01

Profile Slices

Return only the parts of a user's CanonIQ profile that a product is scoped to receive, such as decision style, values, timing context, preference signals, and consent scope.

Example
GET /v1/profile-slices/{user_id}
Beta02

Personalization Directives

Translate identity intelligence into practical guidance for product behavior, messaging, recommendations, onboarding, and user experience.

Example
GET /v1/directives/{user_id}
Beta03

Consent and App Permissions

Let users control which products can access which parts of their CanonIQ profile, with per-app scope and per-field controls.

Example
GET /v1/permissions/{user_id}
Beta04

Recommendation Context

Give recommendation systems better context so they can suggest content, products, opportunities, resources, or next actions that fit the person.

Example
POST /v1/recommendation-context
Beta05

Fit and Conversion Signals

Help products understand what message, offer, timing, or action is most likely to land with a specific user.

Example
GET /v1/fit-signals/{user_id}
Beta06

Source Evidence

Attach source-backed context to profile claims so products can understand why a signal exists and whether confidence is high enough to use.

Example
GET /v1/evidence/{claim_id}
Beta07

Explain Why

Generate plain-language explanations for why a recommendation, route, offer, or next step fits the user.

Example
POST /v1/explain
Beta08

Export and Portability

Allow users to export or carry approved parts of their CanonIQ profile across Lumenfolk products and future partner experiences.

Example
GET /v1/export/{user_id}
Tested across the Lumenfolk prototype ecosystem
Developers

Built for developers. Designed for product outcomes.

CanonIQ API gives your product context-specific profile intelligence that can be used by your recommendation engine, workflow, UI, ad system, or preferred LLM.

Privacy by design. CanonIQ does not expose the full person by default. Products request only the profile slices needed for the experience.
canoniq.ai · v1
200 OK
GET/v1/profile-slices/{user_id}
{
  "decision_style": "evidence-informed",
  "values": ["trust", "quality", "time-saving"],
  "preference_signals": ["premium-but-practical", "low-friction"],
  "timing_context": "passive_discovery",
  "consent_scope": "commerce_recommendations",
  "confidence": 0.82
}
Ecosystem

CanonIQ powers the Lumenfolk prototype ecosystem.

The API is designed to provide identity-aware personalization across multiple product surfaces, from recommendations and commerce to career positioning and operating intelligence.

CanonIQ is the shared identity intelligence layer behind Lumenfolk's product prototypes. Each surface tests a different use case for the same underlying system: how profile slices, intent signals, values, decision style, context, and timing can make software more useful from the first interaction.

These prototypes are beta learning surfaces. They are examples of where CanonIQ can go once the shared backend and API layer are fully hardened.

All prototypes are in beta. Outputs are examples and may not represent final product behavior. The purpose of these surfaces is to test intent signals, personalization patterns, and the shared CanonIQ intelligence layer.

The front ends exist. The backend is the unlock.

Lumenfolk has already built lightweight product surfaces that demonstrate the breadth of the CanonIQ opportunity. The next phase is hardening the shared backend, profile system, permissions model, and API infrastructure to reliably power consumer products and future partner integrations.

Request a demo
Early use cases

Early use cases

Next Up

Taste and moment-based recommendations.

Opportunity & Resource Hub

Location-aware resource routing based on need, eligibility, and consented context.

Positioned

Career and positioning experiences that start from approved user context.

The Brain

Source-backed operating intelligence: traceable context, decisions, and value signals across an organization's work.

Consumer apps

More relevant onboarding, recommendations, offers, and next actions.

Sample console

Sample CanonIQ Profile Console

CanonIQ includes a profile console where users can manage profile slices, personalization directives, app permissions, source evidence, and export settings.

Beta prototype. Example data only. Console behavior and outputs may not represent the final product.

canoniq.ai/console
Open console
Profile completion
68%

Next: Add a personality framework result

Confidence
72/100

Weighted across personality wallet items and source evidence.

3
App slices configured
5
Personalization directives
8
Source evidence records
Trust

Built around consent, scope, and sensitivity.

CanonIQ is designed around permissioned context. Products should receive only the context needed for the experience they are improving, and users should have ways to understand, correct, suppress, or remove what CanonIQ thinks it knows.

Consent-aware profile slices

Apps only see the profile slices a user explicitly approves for that experience.

Sensitivity labels

Signals can be labeled public, low, private, sensitive, or restricted — and filtered accordingly.

Product-specific scopes

Each product receives its own scoped slice. The full profile is never shared by default.

User correction controls

People can correct, suppress, or remove what CanonIQ thinks it knows at any time.

CanonIQ is not identity verification, biometric authentication, or a mental health diagnosis. It is a personal context and surface-personalization layer.

Read more in the Trust & Privacy Center.

Product family

One context system, three surfaces.

CanonIQ gives the blueprint. The Brain Console governs the context. CanonIQ API lets approved products use that context safely.

The EngineBeta

CanonIQ

The blueprint engine for identity, context, preferences, and consented profile signals.

Explore CanonIQ
The AppPrivate Beta

The Brain Console

The operating intelligence layer for traceable, high-value work. Source-backed context, decisions, artifacts, workflows, and value signals — connected end to end.

Explore the Brain Console
The InfrastructureDesign Partner Beta

CanonIQ API· You are here

The permissioned infrastructure layer for approved products that need safer context-aware experiences.

Request API Demo
TraceLine
  1. Source
  2. Decision
  3. Artifact
  4. Workflow
  5. Initiative
  6. Outcome
  7. Value Signal

The Brain keeps the thread between what informed the work, what was decided, what was produced, who or what contributed, and what value was created.

Currently in beta

Become a design partner.

CanonIQ API is currently accepting early API conversations and design partner requests. We are especially interested in products that need better personalization, safer context portability, smarter onboarding, better recommendations, resource routing, or AI workflow context.

Make your AI product understand people faster.

We are currently accepting a limited number of early API conversations and design partner requests.

Blueprint. Console. API. One governed context system across CanonIQ, The Brain Console, and CanonIQ API.