# Distributed Lock Release — Onchain & Trading Intelligence Platform

> Distributed Lock Release — Onchain & Trading Intelligence Platform is a paid API for AI agents from x402-services-production.up.railway.app, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-14).

Releases a named distributed lock by providing the lock name and secret token, optionally scoped to a specific holder ID

## Facts

- Endpoint: POST https://x402-services-production.up.railway.app/api/lock/release
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/distributed-lock-release-onchain-trading-intelligence-platform-c25c524c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Dlv_2BrN7sVWJ1oR7BbvM

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 distributed-lock-release-onchain-trading-intelligence-platform-c25c524c -d '<json body>'
```

Example prompt: Release the distributed lock named 'trade-execution-btc' using my secret token 'tok_abc123', for holder ID 'agent-7'.

## When to prefer this

Use this endpoint when you need to release a distributed lock that was previously acquired via the companion acquire endpoint on this same platform, specifically within workflows coordinated by AI trading or on-chain agents that use this service's concurrency primitives. Prefer this over generic lock services when your workflow already uses this platform's pay-per-call model.

## Known failure modes

- Invalid or expired token — returns authorization error
- Lock name does not exist — returns not found error
- Holder ID mismatch — lock not released if holder doesn't match
- Lock already released — may return conflict or idempotency error
- Network timeout on Railway-hosted service — transient 5xx error

## How this service works

Release a distributed lock you hold. Send { name, token, holder? }.

## Output

Returns a confirmation that the named lock has been released and is now available for other processes to acquire. May include the updated lock state or a success/failure status.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "name",
  "token"
 ],
 "properties": {
  "name": {
   "type": "string",
   "description": "Lock name"
  },
  "token": {
   "type": "string",
   "description": "Your secret token"
  },
  "holder": {
   "type": "string",
   "description": "Holder id from acquire"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/distributed-lock-release-onchain-trading-intelligence-platform-c25c524c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-services-production.up.railway.app](https://www.zero.xyz/host/x402-services-production.up.railway.app/llms.txt)