What we offer
The assistant runs the workflow. The engine does the numbers.
A client brief becomes a priced, stress-tested, documented structure in one run, ready for your review.
How it works
Work where you already work. One engine underneath.
Chat, your AI assistant, the API and the Structures shelf all call the same engine. The quote, the stress grid and the KID come from one calculation, so they agree by construction.
OpenArrow chat
Conversational structuring
Your AI assistant
61 tools over MCP
API
For platforms and agents
Structures shelf
17 ready templates
Engine
arrowquant
Vectorised end-to-end, deterministic
Daily-calibrated vol surfaces
Forward, discount and funding curves
Monte Carlo and closed form
Quote
Terms, fair value, costs
Risk
Greeks, stress grid, risk indicator
KID & term sheet
PDF, review-ready
Bespoke payoffs
Payoff graphs priced on the same paths
What you get
Four things a desk can point to.
01
The workflow
Brief, price, stress, document, review. One run, one set of numbers.
02
The shelf
Ready templates across protected and yield structures. Copy one, change the terms.
03
The documents
Term sheet and KID with risk indicator, scenarios and costs, from the run that priced the note.
04
The controls
Every engine call logged against the key that made it. Revoke a key and it stops at once.
Why now
Three things changed at once.
Assistants are becoming the desk’s front end.
Teams already brief an assistant before they open a pricer.
Assistants can now call external engines.
Open protocols such as MCP let them hand the maths to a system built for it.
Clients expect tailored, not off-the-shelf.
More clients want products shaped to their goals. Desks can’t hire their way there.
Put one real brief through it.
Bring a request from your desk. We'll take it from brief to reviewed KID with you on the call.