API v1

Governed Solana RPC routing API

InfraBench executes a live probe from the nearest regional runtime, applies latency and slot-freshness gates, and returns either READY with an endpoint handoff or ABSTAIN with machine-readable rationale. Review the evidence methodology.

Quick start: TypeScript

const res = await fetch(
  "https://infrabench-ruddy.vercel.app/api/v1/route?region=Frankfurt,Germany&workload=trading&rttBudgetMs=45"
);
const data = await res.json();

if (data.decision === "READY") {
  const rpcEndpoint = data.winner.endpoint;
} else {
  console.error("InfraBench abstained:", data.rationale[0].message);
}

Quick start: Python

import httpx

response = httpx.get(
    "https://infrabench-ruddy.vercel.app/api/v1/route",
    params={"region": "Frankfurt,Germany", "workload": "reads"},
)
decision = response.json()
print(decision["decision"], decision["rationale"])

Who uses this API

Trading desks

Call /api/v1/route with workload=trading and rttBudgetMs=45. If the decision is ABSTAIN, do not route; log the rationale code.

Indexers

Use workload=indexing. The latency budget is broader, while slot drift remains material to ingestion freshness.

MEV searchers

Use /api/v1/agent/route with workload=mev. The route abstains when required WebSocket evidence is unavailable.

Audit / compliance

Use /api/v1/history to retrieve 7-30 days of provider evidence for SLA verification and vendor review.

Route endpoint parameters

GET /api/v1/history accepts providerId (or legacy provider), optional region, days from 1-30, and metric equal to p95rtt, slotdrift, or score. It returns both the full evidence points and a chart-ready timestamp/value series.

Building on InfraBench

Agent integrations

The agent route uses the latest governed snapshot and returns only decision, endpoint, score, and timestamp. Set X-Agent-Id for caller correlation and read X-InfraBench-Score without parsing the body.

async function endpointForBatch(agentId: string) {
  const response = await fetch(
    "https://infrabench-ruddy.vercel.app/api/v1/agent/route?region=fra1&workload=trading&rttBudgetMs=80&slotDriftMax=3",
    { headers: { "X-Agent-Id": agentId } }
  );
  const route = await response.json();
  if (route.decision !== "READY" || !route.endpoint) {
    throw new Error("InfraBench abstained; halt or use the configured fallback.");
  }
  return route.endpoint;
}

Errors and rationale

HTTP 400 indicates invalid parameters, 429 indicates rate limiting, and 500/503 indicates unavailable infrastructure. READY and ABSTAIN both return HTTP 200. Treat rationale codes ending in _FAILED or _MISSING as explicit governance blocks; do not infer an endpoint when winner is null.