Skip to content

Developers

AI agents and developers can read Rayon Insurance’s guides and send a request for a visitor without opening the site. Everything here is public. There is no login and no API key.

A request sent this way is the same as one sent through a form on the site: a person replies by email within two business days. Nothing is bound or quoted by the API. Rayon Insurance is a licensed insurance producer in Illinois. Coverage depends on each policy’s terms, conditions and exclusions.

REST API

Base address https://rayoninsure.com/api/v1. JSON in and out. Described in /openapi.json.

GET /api/v1/guides?q=&limit=
Search the guides. Every word in q must appear. Leave q out to list them all.
GET /api/v1/guides/{slug}
One guide, with its full text as Markdown.
GET /api/v1/firm
Who Rayon Insurance is, where it is licensed, what it does not do, and how to reach it.
GET /api/v1/forms
Each kind of request and the page where a visitor fills it in.
POST /api/v1/requests
File a request for a visitor who asked for it. Returns 201.
curl -X POST https://rayoninsure.com/api/v1/requests \
  -H "Content-Type: application/json" \
  -d '{
    "kind": "operators",
    "name": "Dana Reyes",
    "email": "dana@example.com",
    "company": "Example Fulfilment LLC",
    "message": "Signing a RaaS agreement for 12 AMRs at our Joliet site next month.",
    "visitor_confirmed": true
  }'

Kinds of request

operators
A company running robots wants its insurance and robot contracts reviewed, with quotes for any gap.
brokers
A retail broker wants a placement partner for a client deploying robots.
integrators
A robotics integrator wants the customer-side insurance checklist for its SOW.
sellers
A marketplace seller needs to meet a seller agreement's insurance requirement.
contract_review
Send a contract (RaaS agreement, SOW, site-access agreement) to be read against the company's insurance.
agency_servicing
A commercial insurance brokerage wants help with servicing work (Rayon Ops).

Send visitor_confirmed: true only after the visitor has seen what will be sent, agreed to be contacted and to the privacy notice, and asked you to send it. Documents cannot be attached; the reply says where to email them.

Retries and limits

Send an Idempotency-Key header, such as a UUID, with each request. If you retry with the same key and email within 24 hours, you get 201 again with Idempotent-Replayed: true and nothing is filed twice. The same key with a different email gets 422.

Each email address can send five requests in any 24 hours. Responses to POST /api/v1/requests carry RateLimit-Policy and RateLimit headers saying how many are left; at the limit you get 429 with Retry-After. The read endpoints have no limit of their own.

MCP servers

Two Model Context Protocol servers, Streamable HTTP, no authentication. Add either address to Claude, ChatGPT or any MCP client.

https://rayoninsure.com/mcp
get_firm_details, list_request_forms, submit_request, search_insurance_guides. Card at /mcp/server-card.
https://rayoninsure.com/mcp/docs
search_insurance_guides, read_insurance_guide, and every guide as a Markdown resource. Card at /mcp/docs/server-card.

In the browser, every page also registers WebMCP tools (search_insurance_guides, get_firm_details, open_request_form, submit_request) for agents that support it.

Errors

Every error from /api/v1 is RFC 9457 problem details, sent as application/problem+json with type, title, status, detail and code.

400 invalid_request
The request is missing something or has a field that is not valid.
404 not_found
Nothing exists at this address.
422 idempotency_conflict
This Idempotency-Key was already used for a different request.
429 rate_limited
Too many requests from this email address today.
500 server_error
Something went wrong on our side.
503 unavailable
Requests cannot be saved right now.

Versions

The version is in the address. Within v1, fields are only added, never removed or renamed. A breaking change gets a new address, /api/v2, and v1 keeps working for at least 90 days after the change is announced in Deprecation and Sunset headers on its responses. Every response carries an API-Version header.

Files for agents

Every page is also available as Markdown at its address plus .md.

Questions

Email siddansh@rayoninsure.com.