Skip to content

One API. Every caller gets the same surface.

A leasing page, a property management system and an AI assistant all call the same 25 or so tools. Underwriting, issuance, draws and the ledger are addressable. The deposit still gets underwritten by us.

OpenAPI spec →/llms.txt

Request a certificate in one call.

Create the depositor, send the invite, then poll or subscribe for the result. Sandbox keys issue real-shaped certificates against a test bank.

  • Bearer keys scoped to one organisation
  • Webhooks on every status change
  • Idempotent requests and cursor pagination
  • OpenAPI 3.1; SDKs on request
curl https://api.standby.io/v1/certificates/request \
  -H "Authorization: Bearer sbk_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "depositor": { "name": "Jane Doe", "email": "jane@example.com", "phone": "+15550100" },
    "reference_address": { "street": "123 Main St", "unit": "4B", "city": "Boston", "state": "MA", "zip": "02101" },
    "deposit_amount_usd": 2000,
    "term_months": 12
  }'

# → { "request_id": "req_7Kq2…", "status": "invited", "verify_url": "https://app.standby.io/verify/…" }
{
  "mcpServers": {
    "standby": {
      "url": "https://app.standby.io/api/mcp",
      "headers": { "Authorization": "Bearer sbk_live_…" }
    }
  }
}

Connect Claude, Cursor or any MCP client.

Streamable HTTP with OAuth. The tool list is discoverable with a standard tools/list call, and every tool reads through the same access checks as the dashboard.

Onboarding
  • org_onboarding_start
  • org_kyb_submit
  • beneficiary_bank_account_add
Certificates
  • certificate_request_create
  • certificate_request_watch
  • certificate_get
  • certificate_list
Depositors
  • depositor_notify
  • certificate_request_status
Draws (named claim in the API)
  • claim_create
  • claim_get
  • claim_list
  • claim_retry
you ›
→ create_depositor ✓ dep_7Kq2 created
→ request_certificate ✓ invite sent
→ get_certificate ✓ status: active
Certificate active. $2,000 coverage, 12 months. No integration project, no dashboard.

An AI assistant can issue a certificate. So can your leasing system.

About 25 tools sit behind one API. A property management system, a leasing page and an assistant talking over MCP all call the same thing, and the deposit is still underwritten by us.

MCP server

Issue and manage certificates from Claude, Cursor or any MCP client.

REST API

Underwriting, issuance, draws and the ledger.

Developer docs →

Where the deposit already lives.

Standby integrates directly with your property management system. Invites go out from the system your leasing team works in, and Standby posts directly to the ledger.

Want to know about your system? Tell us what you run. The API covers everything an integration does.

Sandbox keys in a day.

Email hello@standby.io with what you are building.

Book a demo →hello@standby.io