Developer resources
Give your AI a better understanding of the person on the other side.
Fluence turns interaction patterns into a structured behavioral context object that applications can use at decision time. Start with one journey and one decision your product needs to make more relevant.
Discuss an integrationDocumentationGET/context/{user_id}200 OK · ~20ms
Illustrative response example
Integration
The integration contract
Your product sends the interaction signals it already generates. Fluence normalizes them into a behavioral event stream, models tendencies and current state, then returns model-ready context through a single API call.
01
Your product
Signals you already emit
02
Fluence
Events → tendencies and state
03
Your application
Decision-ready context
GET /context/{user_id}
Returns a model-ready context block with behavioral tendencies, current state, decision patterns, and confidence levels for each inference.
Evaluation
What your team evaluates
01
Choose one decision
For example: which support response, checkout intervention, or recommendation should happen next?
02
Connect existing signals
Use the interaction events your application already creates, such as timing, navigation, revisits, and uncertainty signals.
03
Apply context with guardrails
Your application decides how to use a confidence-scored context signal; Fluence does not make the final decision.
Built for bounded inference
Fluence analyzes interaction patterns, not the private content a person types, views, or says. Behavioral context is a probabilistic input with confidence levels, not a definitive label about someone.
Customer documentation
Full API reference, authentication guidance, and account-specific integration material are available in the customer documentation portal. Access requires a Fluence customer session.
Open customer documentation
FAQ
Frequently asked questions
Is the developer documentation public?
The public resources on this page explain the integration model. Full API reference and account-specific documentation are available to authenticated Fluence customers.
What does GET /context/{user_id} return?
A structured behavioral context block for an application or model to consume. It includes tendencies, current state, decision patterns, and confidence levels for inferences.
Does Fluence replace our analytics stack?
No. Fluence is designed to use the interaction signals a product already generates and add an interpretation layer alongside analytics, CDPs, and decision systems.
How long does integration take?
In the reference pilot, integration was completed in under 10 hours. Actual time depends on which interaction signals your product already generates and the decision you start with.
What data do I need to send?
The interaction events your application already creates, such as clicks, timing, navigation, revisits, and uncertainty signals. You don't need to send what a person types, views, or says.
Does Fluence work with any AI model?
Yes. Context is delivered as a structured block any application or model can consume. The profile belongs to the person, not to a specific model, so it can be used across systems.
How does Fluence handle LGPD and GDPR?
Fluence analyzes behavioral patterns, never content, and is designed for LGPD and GDPR compliance from the start. Every inference carries a confidence level rather than a definitive label.
Start with one decision. Prove the impact.
Tell us which decision your product needs to improve and we'll design the integration with you.