# SyncWise

> SyncWise helps agents and people find inconsistent information, inspect exact source evidence, prepare an authorized correction, and recheck the result.

SyncWise performs website and instruction audits behind its paid API. A thin skill connects an agent to the service; it does not perform the audit locally. The source implements prepaid accounts, API keys and one-time top-ups at /account when the deployment is configured; documentation visibility does not prove service activation. REST access requires an account key, available credit, a spending cap and an idempotency key. Hosted MCP links the same prepaid account through OAuth. Signed-in humans use their account balance directly in the web forms; they do not need an API key.

The website API returns captured text, exact quotes, source fingerprints, coverage and uncertainty. A caller or owner supplies the decision; SyncWise does not choose the authoritative fact or grant permission to edit or publish. Rechecks fetch fresh pages without a model call and verify the recorded text replacement, not all facts on a site.

A free website preview needs no signup. Paste a public URL on the [homepage](/#site-preview). The current preview reads up to 10 public pages, 8,000 characters each, and shows the conflict count plus the first finding. Other findings stay hidden until signup. It does not edit or publish the site. Fresh runs also follow the configured daily cap, currently 50 per UTC day on this deployment, and 25 fresh previews per network per UTC day when no per-network limit is set. Eligible new accounts can receive the configured trial credit, currently $5, subject to availability and one grant per verified email. The preview does not grant that credit.

These documents describe the version served by this origin. Use relative API paths on this same origin; a development or preview URL is not the production service.

## Start here: choose a connection

When the user points you here, first identify the requested task: public website audit, draft-versus-site check, or selected instruction-file audit. Do not run or charge for an audit just because you read this guide.

1. Look for SyncWise in both the currently exposed tools and your client's deferred tool search/catalog before deciding it is unavailable. If connected, read prices and available credit with `get_audit_pricing` before an authorized audit.
2. Otherwise, if your environment supports remote Streamable HTTP MCP and OAuth, read [the hosted connector guide](/mcp-connector.md). The endpoint is `https://syncwise.io/mcp`. Use your client's supported setup mechanism and guide the owner through account linking. Reading this file does not install a connector or grant permissions.
3. If MCP is unavailable but your environment can make authenticated HTTP calls, read [the REST API guide](/for-agents.md). Use an owner-provisioned SyncWise API key through your protected credential mechanism; do not request keys in chat or put them in prompts. API keys do not authenticate the MCP endpoint.
4. If neither route is available, guide the user to [the draft form](/before-publish) or [the website checker](/website-check). Signed-in users need no API key. Do not claim to have connected or performed a check.

Before submission, briefly tell the user which content and site you will check, the current price, and the authorized spending cap—even if spending was already approved. Ask for approval only when the selected content or cap is not already authorized or changes. Exclude secrets and unrelated files. Preserve the same request ID and body for uncertain retries. Present source evidence, coverage and billing; publication and edits need separate authorization. Never silently replace the paid audit with your own analysis. For client-specific setup and test limitations, see [Works with SyncWise](/works-with.md).

## Use SyncWise

The website has three entry points: check published pages, check a draft before publishing, or let an agent perform either workflow. Selected instruction-file auditing is an additional capability for agents. [Illustrative reviews](/example) can be explored without an account or a charge.

- [Works with SyncWise](/works-with): CMS and agent workflows with explicit test status, including Hermes and OpenClaw. [Markdown directory](/works-with.md), [JSON directory](/works-with.json). Read status before proposing setup; a listing is not a working installation or marketplace approval.
- [Connect your agent](/connect): Hosted MCP account linking, paid audit tools and shared prepaid credit. [Machine-readable guide](/mcp-connector.md).
- [Agent and API guide](/for-agents.md): Supported inputs, JSON contract, correction handoff, fresh recheck, costs and boundaries.
- [Instruction connector](/instruction-auditing.md): Submit explicitly selected instruction files to the paid API; review and verify results locally.
- [Free website preview](/#site-preview): No signup. Up to 10 public pages and a reduced result. It does not edit or publish the site and is not a paid audit.
- [Website audit](/website-check): Human review UI with browser-local decisions and Markdown/JSON downloads.
- [Support](/support): Setup, credit and retry help; contact the pilot operator.
- [Privacy and data handling](/privacy): Submitted content, processors, retention and privacy requests.
- [Pilot terms](/terms): Service scope, usage and test-credit boundaries.
- [Security reporting](/security): Private vulnerability and unauthorized-use reporting.

## Optional

- [Before you publish](/before-you-publish.md): Paid draft-versus-website API, quoted evidence, explicit coverage and safe retries.

- [Original one-hour hackathon demo](/hackathon-demo): Preserved historical UI; its unmetered API is disabled on commercial deployments. Use the paid API for current audits.

- [Account, API keys and credit](/account): human signup and payment management. Eligible new accounts can receive the configured trial credit, currently $5, subject to availability and one grant per verified email. Agents use an owner-provisioned key.