01 / eventSomething happens
A lead arrives, a task changes, a document lands, an alert fires or a tool proposes an action.
Real-world reflexes
Leads, customer messages, documents, tasks, alerts and research events all share the same pattern: something happens, a small decision is needed, and the rest of your workflow keeps control.
Explore all 26 public use cases →A new lead arrives
Compare bounded lead facts with an explicit ICP before spending sales time.
A customer message arrives
Recommend the right handling branch without sending a reply or changing the ticket.
An invoice is normalized
Run arithmetic and exact validation first, then classify the remaining semantic exception.
A task enters the queue
Make a cheap scheduling decision from bounded context before waking expensive work.
An operational signal changes
Classify handling depth after hard severity thresholds and known signatures have run.
A research claim is proposed
Decide whether bounded evidence supports continuing or needs further verification.
You decide what happens next. Reflex does not send the email, approve the payment, click the button or deploy the change. It gives your system evidence it can use immediately.
01 / eventA lead arrives, a task changes, a document lands, an alert fires or a tool proposes an action.
02 / reflexIs it worth attention? Which route fits? Does it pass? How risky is it?
03 / decisionYour workflow receives a typed recommendation and keeps policy, budget and side effects local.
Start from an official recipe, one of the public examples, or a Binary, Choice or Score template. Custom Reflexes stay private to your Organization.
See templates and recipes →Decide whether an event deserves expensive agent work.
Recommend a route inside a deterministic candidate allowlist.
Find removable semantic context without touching pinned/system state.
Advisory semantic risk before deterministic tool authorization.
Pass, review or stop — without mutating or delivering protected output.
For builders
The Reflex registry, schemas, templates, examples and SDK are Apache-2.0. The hosted Brida control plane is a separate service. Idempotency is part of the API contract, so retries recover the same logical decision.
curl https://api.brida.ai/v1/reflexes/agent-wakeup/runs \ -H "x-api-key: $BRIDA_API_KEY" \ -H "Idempotency-Key: wakeup-001" \ -H "Content-Type: application/json" \ -d '{"state":{"source":"github","event":"check_run","conclusion":"failure"}}' Free Decision Capacity
Get enough bounded capacity to find a real use case and reach first value. We do not silently consume paid fallback when it runs out.