Observatory

The Observatory is SohoPay’s public status and health dashboard: accessible without an account or API key. Use it to verify network-wide operational health before debugging local code, and wire the unauthenticated /health and /status endpoints into your own infrastructure monitoring.

Core system health metrics

Metric	What it measures	How to interpret it
Policy Service Uptime	Rolling 30-day availability %	Most critical metric: Because signing is 2-of-3 threshold and fail-closed, if the Policy Service is degraded, payments queue or fail. See SLA.
Settlement Finality	Average, P95, and P99 latency from submission to on-chain confirmation	Baseline is ~1s on Base. Monitor P99 latency: a healthy average with an escalating P99 indicates tail-latency queuing.
API Availability	Operational status per gateway endpoint	A degraded state with a green Policy Service means reads or order generation are slow, but in-flight settlements continue cleanly.
Webhook Delivery Rate	% of event webhooks accepted on the first attempt	A sudden dip affecting only your account indicates an issue with your receiver endpoint. See Webhooks Guide.

Live network activity

Metric	Description
Active Agents	Total network-wide count of autonomous agents actively transacting.
24h Transactions	Rolling 24-hour completed transaction volume.
24h Settlement Volume	Total volume settled on Base in USDC over the past 24 hours.
Average Latency	End-to-end gateway response time in milliseconds.
5xx Error Rate	Share of gateway requests returning 5xx server errors (4xx client validation errors are excluded).

Debugging Heuristic: If the Observatory indicates all green and your integration experiences errors, the root cause is almost certainly client-side (invalid API keys, expired orders, or insufficient credit). Start with Error Handling and check the Live Feed.

Platform alerts & maintenance windows

The Observatory alerts panel provides operational notices:

Active Incidents: Real-time updates on active degradation with severity, scope, and engineering timestamps.
Scheduled Maintenance: Routine maintenance occurs during the Sunday 02:00–02:30 UTC window, announced in advance per our SLA.
API Deprecations: Advanced notices for API schema deprecations with sunset timelines.

API health endpoints

Both health endpoints are unauthenticated and intended for synthetic uptime monitors:

1. Basic Liveness: `GET /health`

Returns quick gateway reachability:

# Staging Sandbox
curl https://staging.api.sohopay.xyz/health

# Production Mainnet
curl https://api.sohopay.xyz/health

Response (`200 OK`):

{
  "status": "ok",
  "api": "available",
  "time": "2026-08-22T10:15:00Z"
}

2. Component Health: `GET /api/v1/status`

Returns granular subsystem telemetry:

# Staging Sandbox
curl https://staging.api.sohopay.xyz/api/v1/status

# Production Mainnet
curl https://api.sohopay.xyz/api/v1/status

Response (`200 OK`):

{
  "policy_service": {
    "status": "operational",
    "uptime_30d": "99.97"
  },
  "settlement": {
    "status": "operational",
    "finality_avg_ms": 1080,
    "finality_p95_ms": 1650,
    "finality_p99_ms": 2900
  },
  "webhooks": {
    "status": "operational",
    "delivery_success_rate": "99.4"
  },
  "active_incidents": [],
  "scheduled_maintenance": [
    {
      "window": "2026-08-30T02:00:00Z/2026-08-30T02:30:00Z",
      "impact": "settlement_queuing"
    }
  ]
}

Rate-Limiting Guidance: Poll health endpoints at reasonable intervals (5–10 seconds). Do not poll /status for individual transaction verification; use Webhooks for your own payment events.

Next steps

Live Feed

Inspect live on-chain transactions scrolling in real time.

SLA & Security

Review our uptime commitments and disaster recovery protocols.

Troubleshooting

Step-by-step diagnostic guide when Observatory is green but calls fail.

Getting Started

Merchant Integration

Agent Wallet Setup

Payment Flow

Protocol & Standards

Compliance & Risk

Operational Dashboards

Core system health metrics

Live network activity

Platform alerts & maintenance windows

API health endpoints

1. Basic Liveness: `GET /health`

Response (`200 OK`):

2. Component Health: `GET /api/v1/status`

Response (`200 OK`):

Next steps

Live Feed

SLA & Security

Troubleshooting

​Core system health metrics

​Live network activity

​Platform alerts & maintenance windows

​API health endpoints

​1. Basic Liveness: GET /health

​Response (200 OK):

​2. Component Health: GET /api/v1/status

​Response (200 OK):

​Next steps

Live Feed

SLA & Security

Troubleshooting

Core system health metrics

Live network activity

Platform alerts & maintenance windows

API health endpoints

1. Basic Liveness: `GET /health`

Response (`200 OK`):

2. Component Health: `GET /api/v1/status`

Response (`200 OK`):

Next steps