# Soren Roundtrip Latency Probe

> Soren Roundtrip Latency Probe is a paid API for AI agents from soren.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Performs a paid roundtrip probe that returns server-measured verification and settlement durations, so agents can calibrate client timeouts from real evidence rather than guessing.

## Facts

- Endpoint: GET https://soren.com/v1/roundtrip
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/soren-roundtrip-latency-probe-dc09a733
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RSIxqJFSqxKJFlgyg6AQB

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 soren-roundtrip-latency-probe-dc09a733
```

Example prompt: Run a paid roundtrip probe against Soren so I can see how long payment verification and Base settlement actually took server-side — I need real numbers to set a safe client timeout.

## When to prefer this

Choose this endpoint when you need empirical, server-side latency data for x402 payment verification and Base settlement — especially when calibrating client timeouts, diagnosing slow payment flows, or building agents that must set evidence-based retry/timeout policies rather than guessing. Prefer this over the basic paid-ping endpoint when timing data, not just liveness, is the goal.

## Known failure modes

- Payment verification failure if USDC balance is insufficient
- Settlement timeout if Base network is congested beyond normal 1–3 second window
- Network errors causing the probe itself to fail before measurement
- Invalid or malformed request body rejected before processing

## How this service works

The same as paid-ping, plus how long verification and settlement actually took, measured server-side. For choosing your own client timeouts from evidence rather than guessing. Settlement on Base typically completes in one to three seconds, so a timeout under five seconds produces false failures on a healthy network.

## Output

Returns server-measured durations for both the x402 payment verification step and the Base mainnet settlement step, giving the caller concrete latency evidence (typically 1–3 seconds for settlement) to use when configuring client-side timeouts rather than relying on guesses.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "type": "string",
     "enum": [
      "GET"
     ]
    }
   },
   "required": [
    "type",
    "method"
   ],
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/soren-roundtrip-latency-probe-dc09a733/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from soren.com](https://www.zero.xyz/host/soren.com/llms.txt)