Commercial

Return the verified legal identity, corporate contacts, and evidence URLs for DigitalPublic.

Match a prospective need with public DigitalPublic capabilities, illustrative use cases and plans. It has no access to customer projects or private data.

List read, preparation, supervised-write, approval, plan, and module capabilities with explicit qualifications.

Explain controller and processor roles, public AI training policy, private customer data exclusions, controls, DPA, privacy, and subprocessor evidence URLs.

Provide an objective comparison of direct provider MCP servers and DigitalPublic across setup, governance, cross-channel work, and tradeoffs.

Calculate only the value of entered time savings, plan cost, net value, and break-even hours. It never forecasts sales or advertising performance.

List clearly labeled illustrative use cases without presenting them as customer results or performance claims.

Return the current component health and timestamp. Status is measured by an independent monitor hosted outside the platform. Components with no recent evidence are reported as 'unknown' — never assume 'unknown' means healthy. Does not invent uptime history or an SLA.

Return historical uptime for a component, always alongside its data coverage. A high uptime with low coverage is not meaningful, so both values must be reported together. Returns 'insufficient_data' when coverage is too low to publish a figure. DigitalPublic publishes no contractual SLA.

Start an idempotent 14-day trial with up to three active real projects, 2,000 total units, up to five connected tools and supervised write access. Sensitive actions still require human approval. A single passwordless email verifies identity, establishes the portal session and resumes provisioning. Keep the limited statusToken in MCP client state; never paste it into conversation text.

Resume a trial using its limited status token. Returns stable state and nextAction, remaining days, units and connection capacity, plus only safe human links. It never returns email, provider tokens, OAuth URLs, or provider payloads.

Return publication-aware installation options for the authenticated DigitalPublic operational product in OpenAI, Claude Code, and generic MCP clients. Directory URLs remain null until publication is explicitly enabled.

Return the goal-oriented sequence an agent should follow, including every mandatory human checkpoint and the handoff from DigitalPublic Commercial to DigitalPublic.

Explain what DigitalPublic does for humans and AI agents.

List current plans, EUR and USD prices, limits, seats, modules, and checkout mode.

Return one current plan by id.

Compare two or more plans using the canonical catalog.

Recommend a plan from project count, team size, live-data need, distributor status, and write requirement.

List integrations included in commercial V1. Use trialChannels, not the connector id, as channels for dp_commercial_start_live_trial.

Explain authentication modes, scopes, human prerequisites, review state and known limitations for one DigitalPublic connector.

Explain project isolation, scopes, approvals, token revocation, and audit controls.

Report whether the real trial, self-service checkout, and Enterprise proposal onboarding are currently available.

Return an illustrative synthetic report sample without customer data. This is not a service trial and must never be represented as measured customer performance.

Compatibility checkout for paid plans and Enterprise proposals. Use dp_commercial_start_live_trial for evaluation. A human must verify email and complete any payment.

Return the non-sensitive status of a historical checkout or proposal request. For the real trial use dp_commercial_get_live_trial_status.

Legacy credential claim for still-valid historical paid checkout intents. Live trials never deliver an operational credential in chat; install DigitalPublic and use project OAuth instead.

Request an email-verified Enterprise proposal. This does not create a contract or charge.