Solvency oracle · for agents

Solvency an agent can query.

A machine-verifiable solvency feed over MCP and a public API. Before an autonomous agent moves funds, it can check the counterparty and get a cryptographic answer, not a claim.

agent · tool call
// before settling with a counterparty
agent.useTool("solva.check_solvency", {
entity: "orbital-pay"
})
{
solvent: true,
margin_bps: 1240,
proof: "0x7a3f…e3f1",
verified_at: "2026-06-19T09:41Z"
}

Why agents need it

Agents can’t read a PDF attestation.

As software starts to move money on its own, it needs counterparty risk it can evaluate in code, in real time. A quarterly attestation, a press release, or a logo on a website mean nothing to a program. A signed proof on-chain does. Solva turns solvency into a value an agent can fetch, check, and act on.

Two ways to query it.

Model Context Protocol

MCP tool

Drop the Solva MCP server into any agent runtime. The model gets a check_solvency tool with typed inputs and verified outputs.

"mcpServers": {
  "solva": {
    command: "npx solva-mcp"
  }
}
HTTP

Public API

A plain REST endpoint for anything that speaks HTTP. Returns the live solvency status and the proof reference to verify independently.

GET /v1/solvency/orbital-pay
→ { solvent: true, margin_bps: 1240 }

Where it’s used

Pre-trade checks

A trading agent confirms a venue is solvent before routing an order.

Treasury automation

A treasury bot only parks funds with counterparties that prove solvency.

Continuous monitoring

A risk agent watches the margin and alerts the moment it nears a breach.

Give your agents a source of truth.

Wire the solvency oracle into your stack in an afternoon.