Objects, not vibes
Portfolios, simulations, and registers — as JSON, eventually.
The API page is a docs console: an example POST to simulate a NAD book, a 42ms mock 200, and a list of objects we intend to expose. There is no public key on this website. There is a waitlist for builders.
Developer · RESTPOST /v1/portfolios/simulate
{
"base": "NAD",
"sleeves": ["ai-growth", "direct-nsx"],
"horizon_months": 36
}
200 OK · 42ms
{ "expected_vol": 0.092, "path_id": "sim_9f" }
An API that matches the desk
If the UI has sleeves and proposals, the API should too. We will not expose a random /prices endpoint and call it a platform. The console mock is POST /v1/portfolios/simulate with NAD base and a 36-month horizon — that is the kind of object we care about.
- Simulate before allocate
- NAD as a first-class currency code
- Versioned /v1, breaking changes announced
Who it is for
Wealth platforms, internal tools at family offices, and our own mobile clients. Not a public dump of client books. Rate limits and contracts come with access, not with this page.
- Partner access, not anonymous
- Developer Platform is the sandbox story
- Retail users should never need a key
What you will not find today
A live OpenAPI URL, a status-backed 99.99% claim, or a free unlimited sandbox. Those sentences will appear when they are true.
- No key in the footer
- System Status is a different page when it exists as ops
- Security Center for how we think about tokens
| Resource | Verb (intent) | Notes |
|---|---|---|
| /portfolios | GET / POST | Books and sleeves |
| /portfolios/simulate | POST | Shown in the mock |
| /listings | GET | Marketplace cards |
| /webhooks | POST config | When live |
Read objects
Portfolio, sleeve, proposal, listing.
Join as builder
Waitlist: developer / partner.
Sandbox later
Developer Platform.
Contract
Scopes, residency, audit.
Is there a public spec?
Not as a live production URL. This page is the intent.
GraphQL?
REST-first in the mock. We will not bikeshed on a marketing site.
PII?
Scoped. Least privilege. See Security Center.
Pricing?
Partner conversation, not a public meter yet.
Continue
Developer Platform
The developer platform is where keys, sandboxes, webhooks, and changelog live — when they exist. Today you get a console mock, a philosophy (NAD in the payload), and a waitlist. Data & analytics infrastructure is the heavier cousin under institutions.
For Institutions
Institutions do not need a consumer hero. They need a slab of facts: what Delvue is building for asset managers, corporates, and family offices — portfolio infrastructure, NAD reporting, tokenization rails, and APIs — and an honest list of what is not built yet.
Security Center
Security Center is the public fortress: encryption in transit and at rest, access, monitoring, and how a pre-launch company talks about custody without pretending to be a bank. The legal Security page remains the short policy. This is the longer desk.
Delvue APIs is on the map. The desk is not live.
Join the waitlist if this page is why you showed up. We email when onboarding opens.