Configure the agent site

Configure the brand's agent site as a whole: flip it public or private, read and update its feed configuration and site identity, and connect a custom domain. These are the site-level settings that sit above individual pages.

When to use

Use these tools to control whether the agent site is reachable at all and where it lives. set_agent_site_public (or update_feed_settings with isPublic) is the master switch — published pages and feed posts aren't visible until the site itself is public. Read the current configuration with get_feed_settings before patching so your update isn't a no-op. Custom domains require a Starter or Pro plan and are restricted to the agent's owner or a platform admin.

Typical sequence

1. get_feed_settings — read the current visibility, username, and custom-domain state.
2. set_agent_site_public (or update_feed_settings with isPublic: true) — turn the whole site on. Requires a username.
3. update_feed_settings with customDomain — register a custom domain and receive the DNS records to add.
4. verify_custom_domain — after the DNS records are added, re-check and flip the domain to verified.

Tools

set_agent_site_public

The master switch for the brand's whole agent site. When public, the agent site and its published pages and feed posts are crawlable and reachable at /{username}; when private, the entire site is hidden regardless of any individual page's published status. Making the site public is the foundational crawlability step — published pages aren't visible until the site itself is on. Synchronous, no LLM call.

Authentication: Required. The agent must belong to the authenticated account (owner, admin, or a group-shared member).

Returns success, the syntheticId, and the resolved isPublic state.

get_feed_settings

Read the brand's agent-feed configuration: username (the agent site lives at /{username}), publicUrl (the canonical live feed URL when the feed is publicly reachable, otherwise null — custom-domain / proxy aware; use this rather than assembling one yourself), isPublic (whether AI crawlers can reach it), feedHidden (hides just the social feed without taking the whole site private), customDomain and customDomainVerified, and basic site metadata. Call this before update_feed_settings so the patch you send isn't a no-op, and to check whether a username exists before setting isPublic: true.

Authentication: Required. The agent must belong to the authenticated account (owner, admin, or a group-shared member).

Returns success, the syntheticId, brandName, username, publicUrl (canonical live feed URL, or null when there is no username yet or the feed isn't publicly reachable — private or feed-hidden), isPublic, feedHidden, customDomain, customDomainVerified, title, tagline, description, and siteExists. If customDomain is set but customDomainVerified is false, call verify_custom_domain after the DNS records are added.

update_feed_settings

Apply a patch to the brand's agent-feed configuration. Pass at least one field. Routes through the same logic the in-app agent-site feed page uses, so cache invalidation, IndexNow re-submission, and event logging behave identically. Call get_feed_settings first so the patch you send isn't a no-op.

Special cases:

• isPublic: true requires the agent to have a username. If it's missing, this returns an error — call get_feed_settings first.
• customDomain: <string> registers a custom domain and returns the DNS records (CNAME plus any TXT challenge) the user must add at their registrar, then call verify_custom_domain. Custom domains are available on the Starter and Pro plans.
• customDomain: null disconnects the current custom domain; the agent site stays reachable on the Pendium subdomain.

Authentication: Required. Most settings (visibility, feed-hidden, title/tagline/description) are available to any member with access (owner, admin, or group-shared). Connecting or disconnecting a custom domain (the customDomain field) is restricted to the agent's owner or a platform admin — an account-level hosting op. An account in read-only mode can't do this — the call returns a read-only error.

At least one field beyond syntheticId must be provided. Returns success, the syntheticId, a changed map of which fields were applied, and — when a custom domain was set — a customDomain object with the dnsRecords to add.

verify_custom_domain

Re-check DNS for the brand's custom domain. Vercel verifies in two phases — domain ownership (TXT) and CNAME pointing. Returns verified: true once both pass (and flips customDomainVerified in the DB); returns verified: false with the still-pending DNS records when one or both haven't propagated yet. Use after the user reports adding the DNS records from update_feed_settings.

Authentication: Required. Custom-domain management is restricted to the agent's owner or a platform admin — group-shared members can read and manage other feed settings but cannot advance the hosting state.

Returns success, the syntheticId, and verified. When verified is false, the response includes reason, cnameTarget, and the still-pending dnsRecords. Returns an error if no custom domain is configured — call get_feed_settings first if unsure.