What the free Operator API means for a broker desk

The Jet Intelligence Operator API is free for operators. An operator administrator issues a scoped key, reads RFQs assigned to that organization, and posts a quote, alternative, question or decline. The limit is 120 requests per key per minute. The payload includes route, schedule, passenger count and requirements. It does not include passenger names, travel documents or the broker's contact details.

For the broker, the point is the reply, not the transport. Whether the operator answers in the secure portal or through their own commercial system, the response should land in the same comparison. The desk does not have to retype a quote that already arrived as structured fields.

The API does not file a flight plan, release a dispatch, or decide that an aircraft is available. Availability is whatever the operator explicitly sends: confirmed, confirmation required, or unavailable. If the field is omitted, the contract treats it as confirmation required. That default is deliberate. A missing flag must not become a promise.

Vendor-neutral means a developer can connect an authorized system. It does not mean Jet Intelligence ships a certified connector for Leon, FL3XX, Schedaero or any other FMS. Brokers should describe the API as a response path, not as a live schedule feed.

Tell operators the integration is free, the key is shown once, and they only see requests assigned to them. Tell clients nothing about the API. The client sees the proposal. The commercial benefit for the broker is a faster, more consistent reply from operators who already live in another system and will not adopt a second inbox.

Sample requests, the OpenAPI document and a Postman collection are published with the operator launch kit. A broker does not need to implement the API to benefit from an operator who has.