# Soren Distributed Coordination Session

> Soren Distributed Coordination Session is a paid API for AI agents from soren.com, paid per call via x402, $0.25/call, status unknown (last checked 2026-09-15).

Purchase an operation budget (100, 1000, or 5000 ops) to acquire distributed locks, semaphores, shared rate-limit buckets, and monotonic counters for multi-agent fleets

## Facts

- Endpoint: POST https://soren.com/v1/coord/session
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/soren-distributed-coordination-session-689201b9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ko0a1y_RZc6Xc66uJDx12

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-distributed-coordination-session-689201b9 -d '<json body>'
```

Example prompt: I have 10 agents all hitting the same third-party API with a shared quota — buy me a 1000-operation coordination session on Soren so they can share rate-limit buckets and lock jobs so no two agents process the same one twice.

## When to prefer this

Use this endpoint when multiple agents or workers share a single upstream API quota or must not process the same job twice. Prefer it over ad-hoc locking when you need fencing tokens for true mutual exclusion (not just TTL-based locks), when you want predictable per-operation costs at HTTP latency rather than blockchain settlement delays, and when your fleet size justifies bulk operation budgets (100, 1000, or 5000 ops).

## Known failure modes

- Invalid ops tier value (not 100, 1000, or 5000) returns a 400 error
- Insufficient USDC balance to cover the $0.05–$1.00 session purchase fails payment
- Session creation fails if the x402 payment header is missing or malformed
- Expired or exhausted operation budget causes subsequent acquire calls to fail until a new session is purchased

## How this service works

Distributed locks, semaphores, shared rate-limit buckets and monotonic counters for multi- agent fleets. Use it when nine agents share one upstream API quota, or ten workers must not process the same job twice. Buy an operation budget once, then every call runs at ordinary HTTP latency instead of waiting on settlement. Tiers: 100 ops $0.05, 1000 $0.25, 5000 $1.00. Renew and release are always free. Every acquire returns a fencing token: a TTL lock alone is not mutual exclusion.

## Output

Returns a session with a pre-purchased operation budget and a fencing token that provides true mutual exclusion (beyond TTL alone). Subsequent acquire, renew, and release calls consume from this budget at ordinary HTTP latency. Renew and release operations are always free; only acquires consume budget.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [],
     "properties": {
      "ops": {
       "type": "string",
       "examples": [
        "1000"
       ],
       "description": "Tier to buy: 100, 1000 or 5000 operations. Default 1000."
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/soren-distributed-coordination-session-689201b9/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)