European decision model · Prelaunch

Classify.Route.

Deyqo is preparing a European decision API. You define the categories; the intended service classifies text and routes each request.

Try the demo Plan a pilot

01 / document

Incoming message

This month’s payment appears twice on my statement. Could you check the invoice?

Category / JSON output

{
  "category": "billing",
  "handling": "automatic_path"
}

Synthetic example, with no model call

Structured outputs

A result your application can use

Define the expected categories and the human review rule. Your software uses the decision to continue the workflow.

statecategoryhandling

Define the possible choices

The expected format can be a category, a boolean or a choice from allowed actions. Those values form the contract between the model and your software.

API

Human review

Handle ambiguous cases

Your application sets the automation threshold. Requests needing a closer look go to your team; their corrections help evaluate the system.

Demo

Data

Know where processing happens

The European ambition covers the operator, operations and hosting. Providers and retention rules will be part of the launch information.

Data

Common questions

Can I call an API today?

The project is in prelaunch. The demo uses hand-written examples and performs no inference.

Does a structured output guarantee a correct decision?

The format can be valid while the decision is wrong. Quality needs evaluation on your cases, with a rejection category or human review.

Plan a pilot

Describe your use case

Collect the expected categories, volumes and your team’s role in a pilot brief.

Plan a pilot