Skip to main content
Anyone can call Private Clubs. This page covers why your requests need no credentials, and what the fee fields in a response hold.

​
No API keys

Neither the Private Clubs API nor its MCP server takes an API key, an Authorization header or an account. Send a plain request:

​
Fee access

Every successful API response includes fee_access, which says what fee data the response may hold. For calls without a theprivateclubs.com session, which is every call from your server or script, fee_access is locked and the response holds no fee figures.

​
Fee fields

Each club in an API response carries these fee fields:
  • initiation_fee, annual_dues and monthly_dues are always null when fee_access is locked, which covers every call without a site session.
  • fee_views holds four entries: initiation, annual, monthly and firstYear. firstYear covers initiation plus annual dues. Each entry has a kind.
  • fee_tier labels where a figure comes from: verified means the club is the source, estimate means it is an estimate, and none means there is no figure. It can also be null. Everyone receives it, and it is never a figure.
The kind in each fee_views entry is one of: Calls without a site session only ever see none and locked.

​
Fees over MCP

Private Clubs never returns membership fees over MCP. Account holders see fees on each club’s profile at theprivateclubs.com. Where an MCP tool result has a membership_fees field, it holds this message instead of a figure, sometimes followed by a link to the club’s profile:
See Available tools for the tools that return it.

​
Caching

Successful API responses carry Cache-Control: private, no-store, because fee fields can differ from one caller to the next. Do not store responses in a shared cache or CDN. Next: Pricing and limits and the club object.