# Sharvora Service Proof

> Sharvora Service Proof is a paid API for AI agents from sharvora.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Returns a signed delivery receipt confirming successful x402 paid-call flow, including network, release version, and SHA-256 receipt hash.

## Facts

- Endpoint: GET https://sharvora.com/api/v1/service-proof
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sharvora-service-proof-6d5405cf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DmZvnNfw1tr9BluVBLkd_

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 sharvora-service-proof-6d5405cf
```

Example prompt: Run a quick Sharvora service-proof canary call to confirm my x402 payment pipeline is working — I want to see the delivery status, network, and the SHA-256 receipt it returns.

## When to prefer this

Choose this endpoint when you need the cheapest possible end-to-end x402 payment validation ($0.001 USDC) before committing to higher-value paid API calls. It is specifically designed as a canary probe — ideal for smoke testing agent payment pipelines, CI/CD health checks, or confirming x402 infrastructure is operational on Base network. Prefer it over other test endpoints when you need a real signed receipt proving delivery rather than just a connectivity ping.

## Known failure modes

- Payment not received or insufficient USDC — 402 response with no delivery
- Network congestion on Base causing transaction confirmation delay
- Invalid or missing x402 payment header — request rejected before processing
- Sharvora service temporarily unavailable — no receipt returned
- Receipt hash mismatch indicating delivery integrity issue

## How this service works

Use as a low-cost end-to-end x402 canary before higher-value calls. A successful paid response proves Sharvora delivery and returns release, network, time and a response receipt.

## Output

A JSON object containing: status ('paid-delivery-ok' on success), network identifier (e.g. 'eip155:8453' for Base mainnet), product name ('service-proof'), a SHA-256 receipt hash, and the current release version string. Together these confirm that the x402 payment was processed and delivery was completed successfully.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "paid-delivery-ok",
  "network": "eip155:8453",
  "product": "service-proof",
  "receipt": "sha256",
  "release": "1.4.0-rc9-proof"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sharvora-service-proof-6d5405cf/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from sharvora.com](https://www.zero.xyz/host/sharvora.com/llms.txt)