Skip to main content
All examples are in agentscope-examples/jev, in package io.agentscope.examples.jev. Start with synthetic decisions to exercise the Harness, then substitute your own backend and business evidence.

Build once and run multiple examples

From the repository root:
The combined example looks up refund conditions, retrieves authorized evidence, generates a draft that omits a condition, then revises only the text after review fails. The final answer retains the refund conditions. It uses in-memory retrieval, a scripted generation model and synthetic decisions, without credentials or model service calls.

What to expect

The final reply should retain both conditions: the item must be unused and within the seven-day window. The generation model runs three times: propose retrieval, generate an incomplete draft, then rewrite text without tools. Console review statistics confirm the scripted branches rather than online accuracy. To explore one capability, run its standalone scenario below and use the corresponding API guide to replace the inputs and backend.

Run examples by capability

Replace the class name at the end of the previous Java command with an entry below. All run offline by default, except for the local browser example described separately. Scripted probabilities demonstrate status and execution branches; they cannot measure real model accuracy. For benchmark inputs and live backend options, see Evaluate your Harness.

Use a local browser

JevBrowserLocalExample serves a loopback page and uses an explicitly supplied Chromium executable. By default it uses synthetic decisions and does not access external websites or model APIs:
Substitute the browser path for your system. The session visits the policy page, an independent verifier checks its content, and the page and local service close. Browser API

Make live calls

The support example calls the client only with --live. Other ordinary examples have no common live switch: replace the scripted caller and model as shown in each guide. Browser and benchmark programs have their own explicit --live-jev / --live-qwen options. Environment variables alone never switch an offline example to live calls.