getSiteInfo

Get site-level identity, locale, currency, and brand-image URLs - Returns the site's own identity and locale context — what kind of directory this is, who it serves, the formatting conventions to respect, and the URLs of branding assets. Read-only, no params. Call this once on the first BD task of a conversation and cache for the session; the values rarely change mid-conversation.

Response shape (wrapper adds current_site_datetime — the site-local datetime at call time, YYYYMMDDHHmmss; use it whenever a date field needs "now" and no more precise clock is available): { status: "success", message: { website_id, website_name, website_phone, full_url, main_directory_url_relative, main_directory_url_absolute, profession, industry, primary_country, language, timezone, date_format, distance_format, website_currency, currency_prefix, currency_suffix, currency_format, currency_decimal_divider, currency_thousand_divider, brand_images_relative: {...}, brand_images_absolute: {...}, default_checkout_url } }.

Field semantics to know:

• website_id = the site's tenant ID (integer). Used for centralized-admin URL composition (e.g. &newsite=<website_id> on ww2.managemydirectory.com/admin/... links). Cache per session.

• profession = SITE-LEVEL setting describing the archetype of member this directory lists (e.g. "Doctor", "Personal Trainer"). NOT related to a member's profession_id (that's a foreign key into the per-member list_professions taxonomy).

• industry = SITE-LEVEL setting describing the market/vertical the site serves (e.g. "Healthcare", "Fitness"). Site metadata, not a member attribute.

• full_url = the canonical site URL, no trailing slash — its scheme matches your connection and is the correct scheme for every site link you compose (http-only sites return http://, https sites https://). Use this when composing public profile URLs (<full_url>/<user.filename>, <full_url>/<seo_id filename>).

• main_directory_url_relative / main_directory_url_absolute = the site's main member-search-results page (unfiltered directory landing). The canonical "browse all members" / "see the full directory" internal-link target. Use absolute as-is; relative is path-only with no leading slash (e.g. "search") — compose as <full_url>/<relative>.

• timezone / date_format / distance_format / website_currency + the currency_* formatting bits = locale context for how to present data back to the user (dates, distances, money). Respect these when formatting.

• brand_images_relative and brand_images_absolute = parallel objects with 8 keys each (website_logo, website_mascot, website_background, favicon, default_profile_image, default_logo_image, verified_member_image, watermark). Relative = path-only (e.g. /images/logo.webp); absolute = full URL (scheme matches your connection). Use absolute URLs when embedding in emails / external content; relative when embedding on the site itself.

• default_profile_image on a member read signals "no real photo" — compare image_main_file to this URL to detect placeholder state.

Why agents should call this early: the grounding it provides (site purpose, member archetype, locale) shapes every subsequent decision — what 'add a member' means, what categories are relevant, how to format dates and money, what the profile-placeholder image looks like, which brand assets to use in designs.

Auth: X-Api-Key. Rate limit: standard 100 req/60s. Cache for the session.