What exactly is AiVIS Cite Ledger?

AiVIS Cite Ledger is an evidence-backed AI citation audit and remediation system. It measures how AI models, ChatGPT, Perplexity, Claude, and Google AI, interpret, trust, and cite your web content. The result is a 0–100 CITE LEDGER score across ten weighted families (avs-v3), with BRAG evidence-linked findings and prioritized fixes.

How is this different from Semrush, Ahrefs, or Clearscope?

Traditional SEO tools optimize for keyword ranking in traditional search results. AiVIS Cite Ledger audits citation readiness, the specific signals that determine whether AI answer engines retrieve and cite your content. A page can rank #1 on Google and be completely invisible to AI answer synthesis.

What is BRAG and how does it make findings trustworthy?

BRAG stands for Based-Retrieval-Auditable-Grading. It ties every audit finding to a real, traceable element on your page, a specific heading, schema block, meta tag, or content section, each carrying a unique evidence ID. You can open the element, verify the finding, and recheck it after a fix. No black boxes.

Is the free tier genuinely useful, or just a teaser?

The Observer (free) plan gives you a full composite CITE LEDGER score and all ten family scores (avs-v3), so you can see exactly where you stand and which categories are hurting you. BRAG evidence IDs and prioritized fix packs require a paid plan. Three audits per month, no credit card.

Webmcp Policy | AiVIS Cite Ledger

AiVIS Cite Ledger page for webmcp policy. Evidence-backed AI search inclusion and citation readiness guidance.

TLDR

The AiVIS.biz WebMCP Agent Policy defines the security architecture, quota limits, authentication requirements, data protection rules, and acceptable use boundaries for AI agents interacting with AiVIS.biz via WebMCP (Web Model Context Protocol).

What WebMCP is and why this policy exists

WebMCP (Web Model Context Protocol) is the structured interface that allows AI agents to interact with AiVIS.biz in an authorized, sandboxed way. This policy defines the controls that prevent abuse, protect user data, and ensure agent actions stay within consented boundaries.

All WebMCP tool calls run inside the browser security context for the aivis.biz origin. Sensitive actions such as audits or GitHub PR creation are routed through the backend with authentication and quota enforcement. No raw credentials are ever exposed to the browser or agents.

Authentication and per-tier quotas

Most tools require a logged-in AiVIS Cite Ledger account. Actions that change external systems require explicit user authorization. Session tokens are short-lived and scoped to prevent lateral movement.

Quota limits enforce fair usage across tiers. Observer users receive a limited baseline. Starter, Alignment, and Signal tiers receive progressively higher limits for audits, auto-fix PRs, competitor analysis, and citation tests. Enterprise and Agency plans are negotiated via sales.

Additional per-IP and per-session rate limiting applies.
Violations surface as clear error messages with upgrade CTAs.
Allowlisted accounts bypass quota limits for internal and partner use.

Consent is granular and per-tool with Allow Once, Session, and Always options. Users can revoke all agent permissions instantly from account settings. Full usage history is visible in the Agent Tools Dashboard so users always know what agents did on their behalf.

No agent action proceeds without prior user approval.
Tool invocations are logged for security and billing audits.
No sensitive user data is returned in tool responses unless explicitly authorized.

TLDR

What WebMCP is and why this policy exists

Authentication and per-tier quotas

User consent and revocation