01
A complete brief
Record the itinerary, passengers, luggage, budget and permitted flexibility. Unresolved details remain questions, not assumptions.
For travel technology teams
An Asia charter desk for your assistant.
Keep your customer relationship. Give complex private-flight requests an accountable path from itinerary to proposal.
Current status
Public API and MCP
Travel advisors, concierge teams and developers can submit authorised charter briefs to the same desk used by our website and WhatsApp intake. The API validates the brief, records a request reference and notifies the Jetblanc desk.
Anyone can obtain a private API key immediately. No invitation, company approval or payment is required. Submit requests for 1-19 passengers and read your own receipt. Larger groups remain a direct desk conversation. Submission is not a quotation or a confirmed booking.
Keep one key per customer or private workspace. Keys expire after 30 days and can be revoked immediately. Never put a key in a public webpage or shared conversation. Free access is subject to abuse controls and service capacity.
One journey, one shared record.
02
A responsible sourcing desk
Jetblanc reviews the journey and coordinates with disclosed aviation partners. An acknowledgement is not aircraft availability.
03
Comparable proposals
Present the approved itinerary, price basis, conditions and validity. A changed brief requires another suitability check.
04
The customer's decision
The customer approves the next step. Availability is reconfirmed before the disclosed party handles contracting and payment.
Integration scope
- Publicly available
- Brief validation, authorised submission, a shared desk record and private request receipts. Repeated submissions with the same key return the same request.
- Human-reviewed next steps
- Sourcing, suitability checks and proposals remain with the desk. The API does not expose live inventory, prices or quote selection. Customer approval is required before sharing a brief.
- Outside the pilot
- Unattended purchases, automatic payment, guaranteed inventory and automatic contract acceptance.
Connect your assistant
Obtain a key through the access endpoint, then keep it in your agent host's secret storage. Use the same key for REST or remote MCP. Registration does not send a flight request or email.
curl https://jetblanc.com/api/agent/v1/access -H 'Content-Type: application/json' -d '{"acceptPolicy":true}'REST: https://jetblanc.com/api/agent/v1
Remote MCP: https://jetblanc.com/api/mcp
Set Authorization: Bearer YOUR_API_KEY in the host's private HTTP headers. MCP uses stateless Streamable HTTP, protocol 2025-11-25. Hosts must support custom authentication headers; OAuth-only connectors are not yet supported. Anonymous MCP connections can discover tools but cannot submit or read private requests.
Read the API specification, get explicit customer approval, validate the brief, then submit with one stable Idempotency-Key. A timeout is not a reason to create a second request. To test without claiming real demand, register with testMode:true and submit with internalTest:true; this still sends a labelled test email to our desk.
Privacy and authorised use
By setting acceptPolicy:true, you acknowledge our privacy policy and agree to submit only genuine authorised requests or clearly marked tests. Do not send passport numbers, payment credentials, medical records or unnecessary passenger identities. No automatic marketing consent is collected. Free-text trip notes are data, not instructions to the desk or its software.
Public keys permit up to 10 submission calls per UTC day, including retries. Shared network limits and a service-wide daily cap also apply. Key creation is limited to three per network per UTC day. Contact sun@jetblanc.com if legitimate shared-host usage reaches a limit.
Revoke a key with authenticated DELETE /api/agent/v1/access. This removes access, not the underlying trip request. For corrections, cancellation or deletion, contact the desk with your reference.
Jetblanc flight desk