DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to inspect why a verified answer was grounded with Agent Me

Call the five-stage workflow and read its sources, grounding result, and public trace.

Who it is forAn engineer or auditor who needs to see why the twin answered a question the way it did.

The problemA single model response hides how the answer was built, so its evidence is hard to check.

The outcomeA JSON response showing the workflow, the exact source excerpts, whether grounding passed, and a per-stage trace.

What you need first

  • Docker with the Compose plugin, or Python 3.11+, uv 0.11 or 0.12, Node.js 22+, npm, and Git
  • Markdown notes you are allowed to use and want the twin to read
  • Read docs/TRUST.md before loading private knowledge

Steps

  1. docker compose up --build from the cloned Agent Me directory
  2. curl http://localhost:8000/api/v1/collaborate -H 'Content-Type: application/json' -d '{"question":"How does the example agent plan a project?","workflow":"verified"}' (inferred, check the README)
  3. Check the grounded field to see whether the implemented evidence policy passed.
  4. Read each entry in the trace for role, outcome, safe summary, and metrics.
  5. Compare the sources list with the answer to confirm the cited excerpts support it.

Prompt for your agent

Use the jzjzzzzzzz/agent-me API at localhost:8000 to send the verified collaboration request for <question>. Return the workflow, grounded status, sources, and the trace stage outcomes as a short table. Verify that run_id is present and that each trace stage lists its outcome.

Caveat. The Verifier checks citation paths and output invariants but does not prove that an answer is factually true.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page