Iran and Saudi Arabia Open Direct Channel on U.S. Negotiations
Iran and Saudi Arabia spoke directly about U.S. negotiations Thursday — a bilateral channel between two framework-adjacent powers that are not party to the Versailles instrument.
The direct ministerial call between Iran and Saudi Arabia on Thursday — Iranian Foreign Minister Abbas Araghchi and his Saudi counterpart discussing U.S. negotiations and regional developments, Middle East Monitor reported — marks a distinct diplomatic channel opening in parallel with the official framework process. Neither country signed the Versailles memorandum of understanding. Both are positioned as framework adjacents: inside the geographic consequence of any Hormuz governance outcome, outside the signatory architecture that created the framework’s institutional channels.
What the call signals is that both governments are now managing their bilateral relationship specifically in reference to the U.S.-Iran diplomatic track — not merely around it.
What We Know About the Call
Araghchi and his Saudi counterpart spoke by phone Thursday, with the discussion focused on U.S. negotiations and regional developments. The call’s existence and general subject were confirmed; its specific content — any agreements, shared language, or divergent assessments — was not disclosed. Diplomatic calls of this type typically produce a readout that reflects the most anodyne formulation both sides will accept. Thursday’s readout offered topic but not substance.
The timing is precise enough to be meaningful. The call came one day after the Oman-facilitated joint working group completed its first substantive session in Muscat, and on the same day that Secretary of State Rubio was conveying the U.S. position to Gulf partners and European allies across separate bilateral meetings. Neither Iran nor Saudi Arabia sat in the Muscat room. Their bilateral call fills a gap the framework’s architecture did not close.
The Non-Signatory Position
The Versailles framework’s governance architecture has two formal participants: the United States and Iran. The sixty-day verification window created an Oman-facilitated working group as its Hormuz mechanism — a named body with a named mandate, but not a multilateral one. Saudi Arabia, the UAE, Qatar, and Bahrain are all outside the framework’s signatory structure while being among the parties most directly affected by its commercial-transit provisions.
The structural position is not unusual in conflict-resolution frameworks. What makes it notable here is that the parties inside the framework are managing the same physical chokepoint that the parties outside depend on for their primary export routes. Saudi Arabia’s oil moves through Hormuz. Iran’s signatory commitments define the terms under which it continues to move.
The IRGC’s Thursday warning that vessels transiting without Revolutionary Guards authorization would face consequences — issued hours before a cargo ship was struck by an unidentified projectile — underlines why Gulf states positioned outside the framework’s signatory architecture have specific, urgent reasons to maintain direct channels with Tehran. They cannot use the working group. The ministerial call is what is available to them.
What “U.S. Negotiations” Means From Both Sides
The disclosed topic — “U.S. negotiations and regional developments” — carries different practical weight for each government.
For Iran, U.S. negotiations are the framework itself and whatever the sixty-day verification window produces. Araghchi’s ministry is the signatory ministry; the call is an opportunity to read Saudi Arabia’s assessment of how the framework’s implementation is being received regionally — a useful data point for a government that signed an instrument whose full text remains private and whose institutional channels are under scrutiny following Thursday’s cargo ship incident.
For Saudi Arabia, U.S. negotiations include the framework but also the parallel diplomatic circuit Rubio is running through Gulf capitals. Rubio told Gulf partners Thursday that the Iran deal will ensure their security, Al Jazeera reported — a security assurance the framework’s public text does not provide. Whether Saudi Arabia has accepted that assurance, and on what terms it is treating it, is a question Araghchi had specific reasons to ask. Whether Araghchi offered a reciprocal read of Iran’s intentions under the framework is a question Riyadh had specific reasons to seek.
The Gulf Order the Framework Has Produced
The most durable structural outcome of the eight-day post-Versailles period may be the diplomatic activity it has generated outside its own architecture.
The framework enters Day Eight carrying simultaneous unresolved questions on both its primary security tracks. The Hormuz provision has a functioning institutional channel whose Friday session status was unconfirmed after Thursday’s cargo ship strike. The Lebanon provision has no institutional channel. Against that backdrop, the parties with the most to gain from a stable outcome — and the least institutional access to it — are filling the gap through bilateral channels the framework did not create and cannot monitor.
The Iran-Saudi ministerial call is one data point in that pattern. Rubio’s bilateral Gulf-capitals tour is another. Oman’s public statement that future Hormuz arrangements would carry no transit fees is a third — Muscat staking a public position to protect its mediating role from being complicated by a debate over fees that Iranian parliamentary statements had been raising in the same window.
The sixty-day verification window’s most consequential byproduct may not be what it produces between Washington and Tehran. It may be the adjacent diplomatic architecture taking shape between the regional powers the framework chose to leave outside its signatory structure. That architecture has been building since the ink dried on the Versailles instrument. Thursday’s Iran-Saudi call is the clearest single evidence of it yet.
See also: Versailles Day Eight — both fronts unresolved · Oman working group — first session · IRGC rejects Hormuz route, demands authorization
Found this useful? Share it.


