# Vennatta BGP Routing Evidence Brief

> Vennatta BGP Routing Evidence Brief is a paid API for AI agents from vennatta-core.onrender.com, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-21).

Compares two versions of a BGP routing notice, validates network identifiers, and returns bounded evidence with cryptographic hashes of detected changes.

## Facts

- Endpoint: POST https://vennatta-core.onrender.com/api/v1/briefs/bgp-routing?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vennatta-bgp-routing-evidence-brief-a7afa121
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__1Hrmy8yxmNOIIMIsHd8h

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability vennatta-bgp-routing-evidence-brief-a7afa121 -d '<json body>'
```

Example prompt: Compare these two BGP routing notices for me — here's the previous version and the updated one — and give me a validated evidence brief with hashes showing exactly what changed in the routing announcements.

## When to prefer this

Choose this endpoint when you specifically need to compare two versions of a BGP routing notice and require cryptographically verifiable, hash-backed evidence of changes alongside validated network identifiers (AS numbers, prefixes). It is purpose-built for the BGP routing domain, unlike the sibling Vennatta Evidence Compare endpoint which handles generic text comparisons without BGP-specific identifier validation.

## Known failure modes

- Missing or empty current_text or previous_text returns a 400 validation error
- Text exceeding 50,000 character limit per field is rejected
- Invalid URI format for source_url causes a validation error
- Identical texts with no changes may return an empty evidence set
- Service unavailable on Render cold-start may cause timeout or 503
- Malformed or non-BGP text may produce low-confidence or empty network identifier extraction

## How this service works

Compare supplied routing-notice versions and return bounded evidence, validated network identifiers, and hashes.

## Output

Returns a structured evidence brief containing bounded evidence of detected changes between the two routing notice versions, validated and normalized network identifiers (e.g. AS numbers, IP prefixes), and cryptographic hashes linking the evidence to the supplied input texts.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "source_url": {
   "type": [
    "string",
    "null"
   ],
   "format": "uri"
  },
  "current_text": {
   "type": "string",
   "maxLength": 50000,
   "minLength": 1
  },
  "previous_text": {
   "type": "string",
   "maxLength": 50000,
   "minLength": 1
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vennatta-bgp-routing-evidence-brief-a7afa121/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from vennatta-core.onrender.com](https://www.zero.xyz/host/vennatta-core.onrender.com/llms.txt)