Agentic Rag Source

[apat0]

It would be great if we could add an easy way (an agent parameter for example) to add sources in a structured format when we use an agent with local/external knowledge, so we can add those references to the answer and have link with the original doc/link

[pleabargain]

I read your text twice and I still don't understand. Please provide example pseudo code/output

[julianponguta]

It seems that the suggestion is to structure the agent's output in a way that separates references or sources from the main response. For example, if an agent performs a Google search or queries a local/external knowledge base, instead of embedding references within the response text, they would be provided in a structured format separately, allowing users to clearly see where the information comes from.

This wouldn’t just apply to web searches but could be useful in any scenario where an agent processes information from multiple sources and traceability is needed. A pseudocode example might look like this:

{
  "response": "The Sun is a G2V-type star located at the center of the solar system.",
  "sources": [
    {
      "source": "Wikipedia",
      "url": "https://en.wikipedia.org/wiki/Sun"
    },
    {
      "source": "NASA",
      "url": "https://solarsystem.nasa.gov/solar-system/sun/overview/"
    }
  ]
}

[apat0]

I confirm this is what I meant. It would be great having this also for local knowledge.