Audit

Create or resume a verified-account activation workspace after the public audit and signup steps.

Return the backend-owned journey stage, readiness dimensions, and one next best action.

Attach a current public revenue audit artifact. Input requires expectedVersion and auditArtifactId.

Return the GAM or AdSense authorization URL. Input requires provider set to gam or adsense.

Import connected provider units. Input requires provider and expectedVersion.

Save accept, edit, or reject decisions. Input requires expectedVersion and decisions.

Save a placement revision. Input requires expectedVersion and payload.

Map a display placement backup. Input requires expectedVersion, stablePlacementId, provider, and providerId.

Return installation values for the locked revision. Input is empty.

Verify every stable placement container and the inert loader for the locked revision.

Lock the exact mapped revision. Input requires expectedVersion and revisionId.

Run the complete bounded activation preflight for the locked workspace revision.

Verify the required ads.txt and inert Sulvo head-tag ownership evidence.

Submit the proven revision. Input requires expectedVersion and revisionId.

Retag-after-approval journeys: submit the bare site for Google approval (ads.txt ownership only, no tags). Input requires expectedVersion.

Set or change the journey intake answers on the workspace. Input requires expectedVersion plus at least one of mode, goal, retagTiming.

Return the workspace domain to publisher-owned backup-only serving.

Return active-probe, real-page, and remediation status for the latest activation attempt.

Run a public publisher revenue-readiness screen using directional public evidence. Audits ad stacks, ads.txt hygiene, consent readiness, PageSpeed metrics, and unblocked premium ad unit opportunities (such as Sulvo) to recover lost yield.

Submit an unauthenticated Sulvo account application lead through the current signup API. Audit tools remain available without login, API key, or OAuth; ad-unit generation should wait for Sulvo account approval.

Run normal Sulvo signup step 1: verify the publisher domain and create the unauthenticated signup lead.

Run normal Sulvo signup step 2: create the pending Sulvo user/account. The current signup backend requires a password before the account can continue to ads.txt and review.

Run normal Sulvo signup step 3: save optional company information for a pending Sulvo signup.

Run normal Sulvo signup step 4a: fetch the ads.txt lines the publisher must add for site ownership verification.

Run normal Sulvo signup step 4b: verify whether the submitted publisher domain has the required Sulvo ads.txt lines.

Return the current signup status capability. The current signup API has no public approval-status endpoint, so this tool reports that limitation instead of guessing approval state.

Explains how to complete Sulvo signup document review. Document submission is done in Sulvo onboarding - upload monthly earnings proof or connect an AdSense account - not through this connector, which has no access to the user's local files.

Return the public checklist and interpretation notes used by the publisher revenue-readiness screen.

Get comparative yield and CPM industry benchmarks by publisher vertical to compare standard stacks (AdSense and managed wrappers) against Sulvo Premium Ad Units.

Create a Sulvo ad unit for an approved publisher. Requires SULVO_API_KEY (with the inventory:write scope) in the server environment, never passed as an argument — an account owner mints a write-scoped key in the Sulvo dashboard (Account Settings -> API key). The Sulvo account must be approved; the b

Create Sulvo interstitial ad units (tagless) for an approved publisher. Requires SULVO_API_KEY (with the inventory:write scope) in the server environment.

Create Sulvo auto-sticky ad units for an approved publisher. Requires SULVO_API_KEY (with the inventory:write scope) in the server environment.

Delete a Sulvo ad unit by id for an approved publisher. Requires SULVO_API_KEY (with the inventory:write scope) in the server environment. The key's account must own the unit; the backend enforces ownership.

Fetch a Sulvo report (read-only). Requires SULVO_API_KEY in the server environment (a publisher generates it in the dashboard: Account Settings -> API key). Covers by-date, by-date-and-ad-unit, by-domain-and-ad-unit, bot-filtering, bot-scores, invalid-activity, direct-bidder-analysis, and ad-units-b

List the saved Sulvo advanced reports for the account. Requires SULVO_API_KEY (with the reports:read scope) in the server environment.

Create/update a Sulvo advanced report (adUnit, dimensions, or customData), run immediately (emailed) or on a recurring schedule. Requires SULVO_API_KEY (with the reports:write scope) in the server environment. Note: advanced reports are delivered by email, not returned inline.

Delete a saved Sulvo advanced report by id. Requires SULVO_API_KEY (with the reports:write scope) in the server environment.