Browse documentation

Reference · Launch preview. EvaEsi has not launched.

Sources API

Fetch the live source bundle for a prior request while that request remains available in the inference gateway.

On this page

Endpoint#

HTTPEndpoint
GET https://evaesi.dev/api/v1/sources/{request_id}

The nested /api/v1/responses/{request_id}/sources route remains mounted as a compatibility alias. Both routes require the same bearer key used for the original request.

Live retention#

This endpoint is a live lookup, not a permanent archive. The responses API returns sources_url so clients can re-fetch sources while the request remains resident in the gateway. Once the live source bundle is gone, the API returns 404 SOURCES_NOT_FOUND.

Response format#

JSONResponse format
{
  "request_id": "req_123",
  "level": "focus",
  "sources": [
    {
      "url": "https://example.com/report",
      "domain": "example.com",
      "title": "Example report",
      "tier": "t1_authoritative",
      "retrieved_at": "2026-04-20T12:34:56Z",
      "snippet": "Quoted source snippet...",
      "stance": "supports"
    }
  ]
}

Source fields#

FieldTypeMeaning
request_idstringThe original inference request ID.
levelstring?The level the request ran at, when the gateway still has it.
sourcesarrayLive source list for the request.
urlstringCanonical source URL.
domainstringDomain extracted from the URL.
titlestringHuman-readable page or document title.
tierenumSource tier such as t1_authoritative or t3_community.
retrieved_atRFC3339 timestampWhen the source was gathered.
snippetstringShort quoted or extracted source fragment.
stanceenumHow the source relates to the answer: supports, contradicts, mixed, or context.

Errors#

  • 404 SOURCES_NOT_FOUND when the gateway no longer holds live sources for that request ID
  • 503 EVA_UNAVAILABLE when the inference gateway is not connected
  • 401 INVALID_API_KEY and related auth failures for missing, expired, or revoked keys