$ delvue docs --env sandbox
A terminal aesthetic for people who will break the happy path.
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.
POST /v1/portfolios/simulate
{ "base": "NAD", "horizon_months": 36 }
# keys: not issued · sandbox: planned
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" }
Sandbox
Break simulate without touching a household.
Keys
Rotate, scope, expire.
Webhooks
Signed payloads, retries, dead letters.
Changelog
Breaking /v1 is a crime unless dated.
Environments
sandbox / prod, obvious in the hostname.
Examples
NAD payloads in every tutorial.
Developers are a persona, not an afterthought
If mobile and partner portals are real, the platform must be real. This page looks like a terminal because the audience will smell a Bootstrap docs theme from a mile away. Substance still has to catch up to the aesthetic.
- Example-first tutorials planned
- No “coming soon” as the only H1 — you have this map instead
- Status page when ops exists
Data & analytics infrastructure
Warehouses, export jobs, and research feeds may sit behind the same auth. They are not a public BigQuery. If you need a dump, that is a contract.
- Export as a product, not a side CSV
- Research feeds labelled as delayed
- No selling household books
How this differs from Delvue APIs
APIs are the objects. Developer Platform is the place you live: keys, apps, logs. Split so procurement can read one and engineers the other.
- APIs = resources
- Platform = DX
- Both pre-launch
Read APIs
Know the objects.
Join waitlist
Role: developer.
Wait for sandbox
We will not issue toy keys on a static site.
Ship against simulate
Then ask for prod scopes.
| Surface | Now | Later |
|---|---|---|
| This page | Intent + mock | Live docs |
| Keys | None | Scoped, rotatable |
| Sandbox | None | Simulate + listings |
| Logs | None | Request IDs |
Open source SDK?
Not promised. If we publish one, it will have a real repo, not a zip on Drive.
Rate limits?
Will exist. Numbers when they exist.
On-prem?
Unlikely at start. Ask if you are a bank.
Security review?
Security Center + your questionnaire, when we are ready.
Continue
Delvue APIs
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.
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.
Developer Platform 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.