Repeat principal
The book of business that already knows you. Recall every preference, every operator they tolerated, every one they didn't.
FEDERATED SUPPLY · BRANDED RFQ
Your client's intent,
our learning loop.
Federated supply across the operator pool. Vertex re-ranking with returned reasoning codes. Empty-leg subscription feed. Branded RFQ surface for your shop.
§02 · INTENT
Three intents. One spine.
The work brokers actually do isn't transport — it's pattern-matching intent against supply, fast. We classify three.
Empty-leg arbitrage
The opportunistic book. WebSocket feed with reasoning codes returned — close before the principal opens a competing tab.
Charter-of-charter
When the operator you'd quote can't lift it, the spine reroutes. Reasoning codes show why, every time, in plain terms.
§03 · MATCH
RFQ → MATCH, with the reasoning showing.
Every match returns a confidence score and the codes that produced it. No black box. Brokers get the same surface their dispatchers see.
REASON CODES7
§04 · BRANDED RFQ
Your brand on the surface. Our spine underneath.
White-label RFQ at your subdomain. Your wordmark, your colors, your principal-side privacy posture. Same matching, same codes, same federated supply.
rfq.charterworks.com / new
Charterworks est. 2009 · NYC
POWERED BY ONEWAYS · DISCRETE
TEB · Teterboro
SBH · St. Barths
14 May 2026 · 14:30Z
04
Heavy
01 •••• · GLEX 0.94
02 •••• · GL5T 0.88
03 •••• · G650 0.71
Your brand on the surface. Our spine underneath.
§05 · EMPTY-LEG FEED
WebSocket or polled. Reasoning returned.
Subscribe to the federated empty-leg stream. Events arrive with confidence scores and the codes that produced them. Close before the principal opens a competing tab.
- • Auth: HMAC-signed bearer · rotating
- • Transport: WSS · fallback to long-poll
- • Schema: SemVer · v1 frozen May 2026
- • Filtering: server-side by sector, tail class, price floor
- • Replay: 24h window, signed cursors
empty-leg.event.json810 B
{
"event": "empty_leg.posted",
"rfq_id": "rfq_01HV8YZ9JM3TEB-SBH",
"posted_at": "2026-05-02T14:18:42Z",
"sectors": [
{
"from": "TEB",
"to": "SBH",
"departs": "2026-05-14T14:30:00Z",
"arrives": "2026-05-14T18:24:00Z"
}
],
"tail_class": "heavy",
"tail": {
"reg": "N4ZL",
"type": "GLEX",
"seats": 14
},
"operator": {
"hash": "op_3f9c2a",
"aoc": "FAA-135"
},
"principal_hash": null,
"floor_price_eur": 38400,
"list_price_eur": 54200,
"confidence": 0.94,
"reasoning_codes": [
"AOC_VERIFIED",
"RECENT_SECTOR_FIT",
"PRICE_FLOOR_OK",
"SLOT_AVAILABLE",
"CABIN_CLASS_MATCH",
"OPERATOR_DECLINE_RATE",
"PRINCIPAL_LOYALTY"
],
"returned_at": "2026-05-02T14:18:42.317Z",
"expires_at": "2026-05-14T11:30:00Z"
}Wire format. Reasoning codes returned with every event.
§06 · COMPLIANCE NOTE
Brokers don't see principal PII by default.
The broker surface receives an opaque principal_hash per RFQ — never a name, never a tail-side itinerary outside the RFQ window, never billing or contact data. Operators authorize disclosure on a per-flight basis when the broker is the principal's quoting party of record.
On flows where the broker is the principal-of-record (charter agency, family-office travel desk), oneways acts as a sub-processor under the broker's privacy posture. On all other flows we are a data processor for the operator. Two postures, never blurred.
- REGULATIONAOC verified
- DATAGDPR · UK GDPR
- REPORTINGDAC7 ready
- AUDITSOC 2 · ISO 27001
More on data flows and posture: trust → · security.txt →
§07 · KEY REQUEST
Request a broker key.
Sandbox in 48 hours. Production after a short call to confirm volume tier and posture. Serial number returned on submit — quote it back in any follow-up.