# VYTREL Control Research Proof

> VYTREL Control Research Proof is a paid API for AI agents from vytrel-control.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-11).

Returns a signed payment proof confirming a paid VYTREL Control API execution on the Base network via x402 protocol.

## Facts

- Endpoint: GET https://vytrel-control.vercel.app/api/research-proof?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vytrel-control-research-proof-7b7275ed
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_r8s32npxJa1gAjs5Djnqy

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 vytrel-control-research-proof-7b7275ed
```

Example prompt: Can you pull a research proof from VYTREL Control to confirm that my last paid API call went through on the Base network?

## When to prefer this

Use this endpoint when you need cryptographic or structured attestation that a VYTREL Control API call was paid and executed on the Base network via x402. Prefer it over generic payment status checks when you specifically need a proofId-anchored, timestamped capability proof tied to the VYTREL ecosystem.

## Known failure modes

- Payment not confirmed — returns paid: false if the x402 payment has not been processed
- Invalid or missing properties parameter may return an error or empty result
- Proof not found — proofId may be absent if no execution has occurred
- Network mismatch — proof may reference an unexpected chain ID
- Service unavailable — Vercel deployment may be temporarily down returning 5xx

## How this service works

Secure OAuth authorization for VYTREL Control.

## Output

A JSON object containing: ok (boolean success flag), paid (boolean confirming payment), network (EIP-155 chain identifier, e.g. eip155:8453 for Base), proofId (UUID identifying the proof), timestamp (ISO 8601 datetime), and capability (string label describing what was proven).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "paid": true,
  "network": "eip155:8453",
  "proofId": "550e8400-e29b-41d4-a716-446655440000",
  "timestamp": "2026-09-28T14:00:00.000Z",
  "capability": "VYTREL paid execution proof"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vytrel-control-research-proof-7b7275ed/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from vytrel-control.vercel.app](https://www.zero.xyz/host/vytrel-control.vercel.app/llms.txt)