Tyton

Creates a Tyton signup and Connect link for one website. Takes either a saved free audit (audit_id and audit_key, which brings the report along) or site_url, the customer's live https website. customer_approved records that the customer agreed to set up Tyton. Returns authorization_url for the customer, plus a private request_id and poll_token for checking the request's status. The customer can pick the free plan or a paid one; existing accounts with a plan skip that step. The link grants no access and starts no tracking by itself.

Checks a signup and Connect request using its request_id and private poll_token. Returns waiting, unavailable or expired, or, after the site owner approves, this connection's server URL, private server key, public browser key and project. The suggested polling interval is 5 seconds. A connection is not tracking approval or activation.

Permanently deletes the Tyton project connected to this connection, including its keys, setup and stored event history. Requires confirmed: true and expected_url equal to the connected project's current URL; nothing is deleted if they differ. The account subscription and billing, the website itself and the Meta dataset and its data are unchanged. The Tyton snippet or SDK stays on the website until removed, and a browser Pixel already loaded there can keep sending to Meta until it is removed and the page reloads. A Meta request already in progress cannot be recalled. Requires a connected site.

Saves a Meta Conversions API token for the connected site's current Pixel. Takes the Pixel ID plus exactly one of capi_token (the raw token) or sealed_capi_token (a sealed token from the Tyton browser extension, starting with `tyton_sealed_v1.`). The Pixel ID must match the site's saved Pixel. Meta checks the token; an explicit invalid or expired response is rejected, otherwise the token is saved with delivery unchecked. Saves the token encrypted; it is never returned. Does not send a test conversion, approve or activate tracking, or prove delivery. Requires a connected site with an active Tyton plan.

Links an existing Tyton audit report to the connected website's Get Started checklist. Takes the report URL; only a report for this exact website is accepted. A linked report completes the checklist's audit step; it is not proof that tracking works. Requires a connected site.

Reads the connected site's setup state in one compact response: plan approval, installation generation, missing callback sources, intentional pauses and the single next step. Read-only: makes no approval or activation and sends no test events. Callback evidence is not business success or Meta receipt. Verification-only setup works without Meta credentials. Requires a connected site.

無需輸入參數。

Checks whether specific PageView or conversion event IDs from an activated live installation reached Tyton's dashboard storage in the last 24 hours. Takes the installation ID and up to 20 unique event and source pairs. Read-only: sends no events and grants no approval. Verification callbacks are not live events. Reports receipt of the requested events only, not business outcomes, all site traffic, target or generation attribution, or Meta delivery. Requires a connected site.

Returns the private Tyton server SDK download, its SHA-256 checksum and the local-file install steps for the connected project. The download authenticates with the connection's server key; no npm publisher account or access to Tyton's repository is needed. Read-only: does not install, approve, start tracking or send events. Requires a connected site.

無需輸入參數。

Records approval of an unchanged conversion plan proposal, identified by its revision and digest, after the customer explicitly accepted it in chat. Requires confirmed: true and customer_confirmation with scope approve_plan. The connected key can approve only its own project; Tyton records connected-agent provenance, not verified human identity. Stale or changed revisions are rejected. Approval only: does not activate tracking or authorize live Meta events. The customer can also approve in the signed-in report.

Records approval of an unchanged conversion plan proposal plus one start request, identified by revision, digest and request_id, after the customer explicitly accepted that scope in chat. The start runs only after the matching installation has fresh verified callbacks. Requires confirmed: true and customer_confirmation with scope approve_and_start_after_checks. A repeated request_id is treated as a retry of the same request. Requires a paired server key and the approval and execution features. Sends nothing now, bypasses no checks, and does not resume a paused, revoked, changed or restaged installation.

Reads staged callback bindings, observed verification signals and the active or paused installation state for the connected site. Read-only. A verified callback proves receipt only, not business success or permission to send live. A matching pending approve-and-start request activates automatically after every fresh current-key check; otherwise the signed-in owner activates separately. Agents cannot activate manually. Active authorization does not prove live client deployment or Meta receipt.

無需輸入參數。

Stages callback bindings (conversion, target and a browser or server source) for the approved latest plan revision and digest under an installation generation. A matching generation is resumed; staging a new generation pauses the previous installation, clears verification and can cancel a pending start. Each enabled target needs a source, and Purchase requires a server source. Each binding reports through client.conversion(conversionId, targetId, data, {installationId: generation, eventId: stableOccurrenceId, verify: true}) on trusted confirmed success, not on a click, submit attempt or URL query parameter. Browser init with mode:'verify' suppresses automatic PageView and Pixel. A closed widget without a trustworthy success callback is unsupported. Does not activate tracking.

Reads the connected site's current conversion plan draft, its open questions, approval state and review link. Read-only.

無需輸入參數。

Saves a conversion plan draft for the connected site. Does not approve or activate it. document.revision must equal expected_revision + 1; a repeated request_id is treated as a retry of the same change. Document: {schemaVersion:1,revision,conversions:[{id,label,enabled,eventName,targets:[{id,label,origin,path}],success:{kind,description}}]}. IDs are stable lowercase slugs; labels are distinct. Official Meta event names only. HTTPS origins only; a path has no query or fragment. Success kind: confirmed_success, checkout_started (InitiateCheckout only), or unresolved. 1 to 50 conversions, 1 to 20 targets each, 100 total, 32 KiB normalized document maximum. No tracking or verification fields. Returns the saved proposal, its open questions and the review link.

Starts a new free audit session for a URL. Returns a private capability (audit_id and audit_key), revision 0 and an initial request_id for the first evidence save, so a lost save response can be retried safely. Saves nothing. The capability covers only this audit record, not access to the website.

Reads an existing audit using its private capability. Returns recorded context, scoped observations, provenance, component coverage, the current decision with open questions, and the report link. Read-only; does not verify the site's backend or grant access to it.

Saves answers about one audited component to the audit. audit_scope records the customer's choice between continuing the investigation and a public-only audit; availability_expectation records whether unavailable controls are expected. Both must have source human_reported. Earlier topics are kept; a new answer replaces the same topic. A public-only choice allows a partial report without further access requests. Returns the updated audit decision and report link.

Saves bounded runtime evidence to the same audit run: sanitized observations from a real browser, authorized backend inspection or a destination UI, with the consent state and observation time. Does not run a browser or send events. A check whose evidence type does not prove it is stored as unknown. Returns the updated findings and report link.

Connects a Tyton site to this connection using a single-use pairing code from the site's card on usetyton.com (valid for 15 minutes). Returns the site's server key and browser key, shown only once, with configuration examples for common MCP hosts.

Inspects one public page's HTML and saves a partial audit report, without signup. Takes the audit session fields and the page URL, plus optional sanitized HTML supplied by the agent, which is stored as unverified evidence. One session can hold several related components. Returns evidence, limitations and discovery actions, not a full tracking-health verdict.

Discovers or configures reviewed v2 setup for a site. With only a URL it is read-only, needs no Pixel and returns setup guidance. With a real Pixel ID on a connected project, it saves the project's site URL and Pixel ID; switching an existing Pixel or site requires confirm_change. Does not approve, install or activate tracking.

Saves checkout and landing answers (payment provider, landing type and route, checkout domains) for the connected project and returns the reviewed server SDK success-callback contract. Does not install an integration or prove provider support; approval and activation are separate. Requires a connected site.

Reads the connected project's configuration: site URL, Pixel ID, token status and saved checkout answers. Read-only. Configuration and token status are not plan approval, callback verification, activation or Meta receipt. Requires a connected site.

無需輸入參數。

Checks a page's static HTML for Tyton container and Meta Pixel references, using a public fetch or HTML supplied by the agent, and compares them with the connected project. Read-only. Does not verify runtime callbacks, activation, consent behavior or Meta receipt. Requires a connected site.

Reads aggregate browser and server event observations, delivery statuses, and the known-crawler protection mode and counts for the connected site. Read-only. Counts are not unique business conversions, current installation verification or proof of Meta deduplication. Requires a connected site.

無需輸入參數。

Saves code review findings from the customer's repository to the audit: server-side events, dedup IDs, Pixel and container presence, payment provider, framework, backend location and existing Conversions API quality, plus the relative paths reviewed and any inapplicable checks with reasons. Unknown values stay unknown, not failed. Findings are stored as agent-reported, not verified deployed behavior. A group label is a label only; each report stays separate. Returns the updated audit decision and report link.

Returns Tyton guidance on one topic. meta_setup is the dashboard's nine-step Meta checklist (business, dataset, website, Conversions API token, testing), optionally a single step. website_management covers the website selector, per-project agent connections and deletion. Other topics: install, events, dedup, crawler_protection, create_pixel, create_business, consent, pricing, privacy, performance, gtm, platforms, faq. Read-only reference text, not saved checklist state or proof of delivery.