---
title: "One signed bundle of ALL evidence about a transfer"
method: GET
path: "/api/evidence/bundle/{id}"
tags: ["verification"]
---

# One signed bundle of ALL evidence about a transfer

`GET /api/evidence/bundle/{id}`

## Request

- Base URL: `https://api.anygas.xyz/svc`
- URL: `https://api.anygas.xyz/svc/api/evidence/bundle/{id}`
- Auth: none declared

Robyn can answer four separate questions about a transfer — did it happen (on-chain verification), where did every unit of the fee go, was this the better route, and is the delivery time measured or guessed. Making four calls and stitching the answers together is work an agent will skip, and four unrelated JSON blobs are not something a principal can check. This is one call and ONE SIGNATURE over the assembled whole. READ `verdict` BEFORE RELYING ON IT: the bundle verdict is the WEAKEST of its parts, never the strongest — a complete fee breakdown does not make an unverified transfer settled. Components that could not be produced appear as `unavailable` WITH a reason and are listed in `incomplete`; they are never silently omitted, because a bundle missing a check must not read like one that passed.

## Response `200`

Assembled, signed evidence: outcome, fees, counterfactual, delivery basis

- object

---

[API](https://skmtc.dev/anygas/apis/robyn-anygas-api.md) · [All operations](https://skmtc.dev/anygas/apis/robyn-anygas-api/llms.txt) · [OpenAPI document](https://skmtc.dev/anygas/apis/robyn-anygas-api/revisions/9b7498be8304?raw)