For agencies and web studios

Add an attributable fact passport to every client site.

Collect the statements a client stands behind, prove control of the domain, publish one passport for people and agents, then keep it current as part of your service.

Client deliverable

One maintained source, several useful surfaces

The client receives a public passport, an optional visitor widget and machine access through the existing API and MCP endpoint.

Fact passport

Attributable statements with sources, per-fact status, freshness and a version identifier.

Human widget

A small on-site interface that answers within the passport and shows evidence or a refusal.

Agent access

Structured HTTP and MCP operations, so integrations do not need to scrape the client's site.

Agency workflow

From intake to publication, with a clear transfer boundary

One account can maintain multiple client entities within the platform's current technical guardrails. A plan-specific client allowance is not enforced yet and requires owner approval.

  1. 1

    Sign in by email.
    No password or separate agency identity system is required.

  2. 2

    Register a client domain.
    The entity begins at A0 and is not public through the self-service flow until domain control is proven.

  3. 3

    Choose who verifies A0.
    A client can take over another account's unpublished A0 draft by proving domain control. If the agency completes A1 first, this automatic path closes.

  4. 4

    Confirm and publish facts.
    Every statement keeps its source and attestation status. Missing evidence should remain missing.

  5. 5

    Plan published ownership deliberately.
    Self-service transfer of an A1 or higher entity is not implemented. Use the client as verifier before publication, or treat later transfer as a manual integration dependency.

Proof boundary

Verification is specific, not universal

A1 proves domain control. A2 records a provider-confirmed payment tied to the authenticated owner and entity, not payer identity or KYC. A3 matches an organization in a supported registry. A4 records a named declaration over an identified passport version. None automatically verifies every fact.

Partner responsibility: publish only statements the client supports, keep sources and disclosure levels accurate, revoke outdated facts and do not register domains you or the client cannot control.

Start

Set up the first client entity

You can complete passwordless sign-in, A0 registration, A1 verification and passport creation today. Paid Agency lifecycle management remains an integration dependency.