Skip to content

Est. 2018 · SDVOSB · CAGE 827Y8 · UEI G8NFS5UCJ9F7

Onan Capital Inc — Medical Products + Supplies
TIPS — The Interlocal Purchasing System

TIPS 260804 · Vendor 13662 · Oct 31, 2029

Developer & AI agent surface · API-Version 2026-11-01

Onan Capital Inc API & Supplier MCP Documentation

Stateless, zero-authentication REST and Streamable HTTP MCP interfaces enabling AI purchasing assistants, ERP tools, and buyers to verify credentials, search supplies, and submit formal RFQs.

1. Authentication & Discovery Surfaces

All read-only catalog, entity verification, capability statement, and RFQ submission endpoints are open with zero authentication and no API key required. Supply prices are never published online; every RFQ receives an individual written institutional quote with carrier freight shown separately.

2. Supplier MCP & Public REST Endpoints

Available MCP tools on /v1/ai/mcp:

  • get_supplier_profile — Legal entity, CAGE 827Y8, UEI G8NFS5UCJ9F7, NAICS 423450, TIPS Contract 260804, and contacts.
  • check_cooperative_eligibility — Verifies TIPS Contract 260804 (Vendor ID 13662, active through October 31, 2029).
  • search_supplies — Searches Onan SKUs, safety/clinical families, rapid tests, and comparable buyer part numbers.
  • get_catalog_summary — Lists categories and RFQ steps (without unit prices or inventory counts).
  • audit_safety_expirations — Checks upcoming AED, naloxone, epinephrine, or bleeding-control kit replenishment timelines.
  • submit_rfq — Sends an institutional RFQ with buyer contact, line items, and optional comparable numbers; returns a quote reference ID.
curl -sS -X POST https://www.onancap.com/v1/ai/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_supplies","arguments":{"query":"fentanyl"}}}'

Public REST endpoints: GET /api/catalog (live JSON product snapshot), GET /equivalents.json (comparable buyer part numbers), and POST /api/quote (structured institutional RFQ submission).

3. Typed Error Model (RFC 9457 Problem Details)

HTTP 4xx and 5xx REST errors return Content-Type: application/problem+json with a machine-readable code, HTTP status, explanation, and resolution hint. Nonexistent HTML pages requested with Accept: text/markdown return HTTP 404 in text/markdown with recovery links.

{
  "type": "https://www.onancap.com/docs#errors",
  "title": "Endpoint Not Found",
  "status": 404,
  "code": "not_found",
  "detail": "The requested API endpoint does not exist.",
  "resolution": "Review /openapi.json or /docs for valid REST endpoints and /v1/ai/mcp tools.",
  "docs": "https://www.onancap.com/docs"
}

4. Rate Limits & Throttling Headers

Public API and MCP responses emit RFC-standard rate-limit headers so agents can pace requests automatically:

  • RateLimit-Limit: 120 (requests per 60-second window)
  • RateLimit-Remaining and RateLimit-Reset
  • RateLimit-Policy: 120;w=60
  • On HTTP 429 Too Many Requests, callers receive Retry-After in seconds alongside application/problem+json.

5. Versioning & Deprecation Policy

The MCP and versioned API surface uses explicit URL path versioning (/v1/ai/mcp) paired with response header API-Version: 2026-11-01 and X-API-Deprecation-Policy. Before any breaking change or endpoint retirement, Onan Capital publishes at least 90 calendar days advance notice via RFC 8594 Deprecation and Sunset HTTP response headers and updates this page plus /openapi.json.